自从升级到 npm 5 以来，尽管设置了 npm config set loglevel warn，但我的构建服务器上还是收到了无数的 npm fetch GET 200 ... 消息(见下文) >。有新的设置吗？
[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 <a href="https://stackoverflow.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="39574954790c170a1709" rel="noreferrer noopener nofollow">[email protected]</a>
npm info using <a href="https://stackoverflow.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="1977767d7c596f21372a3729" rel="noreferrer noopener nofollow">[email protected]</a>
[0m[91mnpm info lifecycle <a href="https://stackoverflow.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="690410081919440a05000c071d295947594758" rel="noreferrer noopener nofollow">[email protected]</a>~preinstall: <a href="https://stackoverflow.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="a0cdd9c1d0d08dc3ccc9c5ced4e0908e908e91" rel="noreferrer noopener nofollow">[email protected]</a>
[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
[...]
最佳答案
具有 Node 的 Docker 容器通常将 ENV 变量 NPM_CONFIG_LOGLEVEL 设置为 info，而不是默认的 warn。您可以自己设置此 ENV var 或使用 npm install --logLevel warn 覆盖该行为。
关于node.js - 在 npm 5 中调用 install 时如何避免 "npm fetch GET 200"日志，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/45800022/