node.js - How to avoid "npm fetch GET 200" logs when invoking install in npm 5 -
ever since upgrade npm 5 gazillion of npm fetch 200 ...
messages (see below) on build servers despite setting npm config set loglevel warn
. there new setting that?
[0m[91mnpm info[0m[91m config[0m[91m set "loglevel" "warn" [0m[91mnpm info [0m[91mok [0m[91mnpm[0m[91m info worked if ends ok [0m[91mnpm info using npm@5.3.0 npm info using node@v8.3.0 [0m[91mnpm info lifecycle myapp-client@0.0.1~preinstall: myapp-client@0.0.1 [0m[91mnpm http fetch 200 https://registry.npmjs.org/babel-eslint 98ms [0m[91mnpm http fetch 200 https://registry.npmjs.org/babel-eslint/-/babel-eslint-7.2.3.tgz 23ms [...]
docker containers node set env
variable npm_config_loglevel
info
instead of default warn
. can set env
var or use npm install --loglevel warn
override behavior.
wiki
Comments
Post a Comment