• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

npm / cli / #1299 / 1
98%
latest: 97%

Build:
Build:
LAST BUILD BRANCH: nlf/arborist-validation
DEFAULT BRANCH: latest
Ran 20 Feb 2021 04:48AM UTC
Files 118
Run time 7s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

20 Feb 2021 04:46AM UTC coverage: 97.753% (-0.003%) from 97.756%
#1299.1

push

isaacs
Do not print error banner for shell proxy commands

There are a few commands (exec, run-script, and the run-script proxies)
where essentially npm is acting like a very fancy shell.  It is peculiar
and noisy for npm to print a verbose error banner at the end of these
commands, since presumably the command itself already did whatever it
had to do to report the error appropriately.

For example, `npm test` runs a test script, usually outputting test
results.  Having npm then tell me that my tests failed with exit status
1 and print a debug log, is unnecessary and unwanted.

When the error encountered for these commands does not have a non-zero
numeric 'code', then we still print the standard npm error reporting
messages, because presumably something went wrong OTHER than a process
exiting with a non-zero status code.

2883 of 2960 branches covered (97.4%)

Branch coverage included in aggregate %.

5035 of 5140 relevant lines covered (97.96%)

20.3 hits per line

Source Files on job #1299.1
  • Tree
  • List 0
  • Changed 6
  • Source Changed 3
  • Coverage Changed 5
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 1299
  • 5287b6e4 on github
  • Prev Job for on isaacs/quieter-exec (##1298.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc