Default: false Type: Boolean If set to true, then npm will stubbornly refuse to install (or even consider installing) any package that claims to not be compatible with the current Node.js version. The command to run for npm edit or npm config edit. How can the CLI team reproduce the problem? Try running npm install to a custom registry with an invalid SSL certificate. The corporate root CA is trusted locally (Windows and Mac keychain etc) but for npm we add a custom certificate bundle via npm config set cafile … and strict-ssl=false as a workaround. Setting strict-ssl=false should workaround this. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly.

npm ERR! network In most cases you are behind a proxy or have bad network settings. Npm ERR! network This is most likely not a problem with npm itself npm ERR! network and is related to network connectivity. npm err! error: no dist in undefined package Check that it’s not a problem with a package you’re trying to install (e.g. This can be caused by corporate proxies that give HTML responses to package.json requests. Run npm cache clean and/or try again later. Possible temporary npm registry glitch, or corrupted local server cache. This repository has been archived by the owner. Npm err! typeerror: cannot read property 'latest' of undefined

Npm config set ssl false