npm-run output is treated as error output

[jasonkarns]

I'm opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don't understand.
• Other (see below for feature requests):

What's going wrong?

How can the CLI team reproduce the problem?

$ npm run --loglevel=error
<exit code 0>
<prints npm scripts to STDOUT>

$ npm run --loglevel=silent
<exit code 0>
<does *not* print npm scripts to STDOUT>

supporting information:

$ npm -v
2.15.1
$ node -v
v4.4.4
$ uname -a
Darwin FatJack-4.local 15.6.0 Darwin Kernel Version 15.6.0: Mon Aug 29 20:21:34 PDT 2016; root:xnu-3248.60.11~1/RELEASE_X86_64 x86_64

I believe that npm run without any args is intended to print the available run scripts. This means that: npm run without any args should print available run-scripts to STDOUT. Which it does. But only if loglevel is error or below. --loglevel=silent does not print any output.

I don't believe that --loglevel should have any effect on the printing of available run-scripts. The fact that it does so, implies that this output isn't really intended as the main output of npm-run. In which case, the output would have been printed to STDERR and not STDOUT.

[npm-robot]

We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.