You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a related note: I was looking for a way to silence any console output from wp-now. Currently, as far as I can tell, the only way to achieve it is by setting the environment variable NODE_ENV to test (checked on startup here). There is a function called disableOutput() but it's not exposed as a CLI option.
The new proposed option --quiet sounds like it's about logging level, as opposed to --verbose. Maybe it could be named something like --no-open, to clarify that it prevents automatically opening the browser on start.
It looks like
wp-now
always opens a browser unless in a Github codespace (openInDefaultBrowser
).Could we get a CLI flag to background
wp-now
after startup and skip opening the browser?Eg, something like:
Use case:
Scripted spin up of both wp-now as a backend and a separate verbose frontend such as vite dev server.
The text was updated successfully, but these errors were encountered: