Npm ERR! network If you are behind a proxy, please make sure that the Npm ERR! network In most cases you are behind a proxy or have bad network settings. cli.js itself.Npm ERR! network This is a problem related to network connectivity. tgz.Ī new loglevel, notice, has been added and set as default. Local tarballs can now only be installed if they have a file extensions. Shrinkwrap and package-lock no longer warn and exit without saving the lockfile. If you want to use different registries for different packages, use scope-specific registries (npm config set Different registries for different unscoped packages are not supported anymore. If you generated your package lock against registry A, and you switch to registry B, npm will now try to install the packages from registry B, instead of A. This means package-lock.json and npm-shrinkwrap.json should now be cross-platform. Package locks no longer exclude optionalDependencies that failed to build. npm will now immediately fall back to cache if possible, or fail.

Running npm while offline will no longer insist on retrying network requests.

cache-min and -cache-max have been deprecated. Npm cache commands have been rewritten and don’t really work anything like they did before. Git dependencies with prepare s will have their devDependencies installed, and npm install run in their directory before being packed. file://path/to/tarball.tgz will not change – only directories are symlinked. packages/subdir will now create a symlink instead of a regular installation. 不要再使用大写的 npm（npm will now scold you if you capitalize its name.

Npm config set loglevel http