Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/npm/cli.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorisaacs <i@izs.me>2021-02-20 07:39:12 +0300
committerisaacs <i@izs.me>2021-02-22 23:30:12 +0300
commit4e58274ed0fd2dd29d3c8d6c7c47f37a37dc0f0f (patch)
treea3e88314ceb246257252307985846a926e839872 /lib/npm.js
parentbe9f1525587d70c909da88b996220b374583d42a (diff)
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. PR-URL: https://github.com/npm/cli/pull/2742 Credit: @isaacs Close: #2742 Reviewed-by: @nlf
Diffstat (limited to 'lib/npm.js')
-rw-r--r--lib/npm.js5
1 files changed, 5 insertions, 0 deletions
diff --git a/lib/npm.js b/lib/npm.js
index 40aa9bbd9..85dc67a78 100644
--- a/lib/npm.js
+++ b/lib/npm.js
@@ -49,6 +49,7 @@ const makeCmd = cmd => {
}
const { types, defaults, shorthands } = require('./utils/config.js')
+const { shellouts } = require('./utils/cmd-list.js')
let warnedNonDashArg = false
const _runCmd = Symbol('_runCmd')
@@ -81,6 +82,10 @@ const npm = module.exports = new class extends EventEmitter {
this.updateNotification = null
}
+ get shelloutCommands () {
+ return shellouts
+ }
+
deref (c) {
return deref(c)
}