`QUIET` / `--quiet` / `quiet: true` should be respected across all modules
See original GitHub issueCurrently we are suppressing logging with the quiet flag for some, but not all modules. We should extend this to all modules and circumstances.
This includes setting the QUIET
env var, the --quiet
CLI flag, and any quiet: true
params where appropriate.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Page 3: Cultural Influences on Behavior - IRIS Center
Students who listen and remain quiet are respectfully engaged. Students who actively participate are engaged. Family engagement. Families who participate in ...
Read more >CLI options - Terragrunt
Learn about all CLI arguments and options you can use with Terragrunt. ... Terragrunt modules and run apply in each one, concurrently, while...
Read more >TypeStrong/ts-loader: TypeScript loader for webpack - GitHub
Beware of the fact that errors are written to stderr and everything else is written to stderr (or stdout if logInfoToStdOut is true)....
Read more >site — Site-specific configuration hook — Python 3.11.1 ...
After this, an attempt is made to import a module named usercustomize , which can perform arbitrary user-specific customizations, if ENABLE_USER_SITE is true....
Read more >Teaching respect for all: implementation guide
Thus, for the Teaching Respect for All message to truly permeate all aspects of ... consequences should not be kept quiet by either...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Will ship in
1.6.0
!The env var problem described in
ARC_QUIET=false arc sandbox
is certainly not unique to us or this project – I’m personally not sweating that scenario fwiw. But it’s good to note, and I pity anyone who generally goes around trying to setfalse
as env var values in bash.