CLI --ci and --quiet options are confusing and not documented/available for static build

[backbone87]

The CLI options --ci and --quiet are a little bit confusing for their intended purpose.

Prefered solution:

• For --quiet i dont expect any output at all, unless there is an error.
• And for --ci i expect everything to be ready to be used in a CI env (no browser launch and no progress/terminal spam)
• Maybe introduce a --no-browser option to disable browser launch (though, you should rly should just use --ci)

Edit: also make both options available to static build (they actually work if buildStatic is called via API, though ofc --ci does nothing currently because its only handled in buildDev)

[stale]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[shilman]

Related #6201

[stale]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[stale]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!