search

mysticatea / npm-run-all

A CLI tool to run multiple npm-scripts in parallel or sequential.
MIT License
5.72k stars 240 forks source link

`--silent` flag isn't working properly #162

Closed ivancuric closed 5 years ago

ivancuric commented 5 years ago

I'm running typescript in noEmit mode to do a typecheck.

"typecheck": "tsc -p .",
"ts:silent": "run-s --silent typecheck",

While npm run -s typecheck works, both npm run typecheck and npm run ts:silent produce an error output:

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! myproject@0.0.0 ts:silent: `run-s --silent typecheck`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the myproject@0.0.0 ts:silent script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/ivan/.npm/_logs/2019-02-11T15_06_16_069Z-debug.log

Using the || true hack isn't an option due to development being done in Windows, and neither is setting up a .npmrc with loglevel=silent

mysticatea commented 5 years ago

Thank you for this issue.

However, this is working correctly. The log you saw is the log of npm run ts:silent rather than run-s --silent typecheck which is silent.

ivancuric commented 5 years ago

Is there any way npm-run-all can help with avoiding the log? Eg, replacing the || hack?

mysticatea commented 5 years ago

No. It cannot affect how the parent process works.