How to avoid "npm fetch GET 200" logs when invoking install in npm 5

Question

Ever since upgrade to npm 5 I get a gazillion of npm fetch GET 200 ... messages (see below) on my build servers despite setting npm config set loglevel warn. Is there a new setting for that?

[0m[91mnpm info[0m[91m config[0m[91m set "loglevel" "warn"
[0m[91mnpm info [0m[91mok 
[0m[91mnpm[0m[91m info it worked if it ends with ok
[0m[91mnpm info using [email protected]
npm info using [email protected]
[0m[91mnpm info lifecycle [email protected]~preinstall: [email protected]
[0m[91mnpm http fetch GET 200 https://registry.npmjs.org/babel-eslint 98ms
[0m[91mnpm http fetch GET 200 https://registry.npmjs.org/babel-eslint/-/babel-eslint-7.2.3.tgz 23ms
[...]

Answer 1

Docker containers with node often set ENV variable NPM_CONFIG_LOGLEVEL to info instead of the default warn. You can set this ENV var yourself or use npm install --logLevel warn to override that behavior.