![npm config set registry not working npm config set registry not working](https://www.tomsquest.com/img/posts/2018-10-02-better-npm-ing/npm_logo.png)
The correct command for changing registry is. npmrc file which is the configuration for npm.
NPM CONFIG SET REGISTRY NOT WORKING INSTALL
Trying to install a few npm packages in my project like express, mysql2. It works on but throws an error on is my npm-debug.log (sensitive info replaced): After executing npm install the sill idealTree buildDeps step takes a long time (minutes) causing email protected working with workspaces slower than email protected installing projects separately. To avoid any errors, ensure strict-ssl=false is set. Try running npm install to a custom registry with an invalid SSL certificate. How can the CLI team reproduce the problem? devDependencies are not installed at the topmost level when running local npm install without any arguments. npm config set bit:registry Or, if using Yarn: yarn config set 'bit:registry' ' Then, you can simply copy-paste the relevant command from the component's page. 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. To install this component as a package all you have to do is to configure bitsrc.io as a Scoped registry for your local NPM client. Setting strict-ssl=false should workaround this. We know our custom registry has an invalid SSL certificate. The registry is protected using a self-signed root CA certificate.
![npm config set registry not working npm config set registry not working](https://user-images.githubusercontent.com/40677509/60547908-bcbd4b00-9cd5-11e9-9765-64c76b55f221.png)
We're using an internal registry via npm config set registry which is behind a corporate proxy. Running npm install on throws UNABLE_TO_VERIFY_LEAF_SIGNATURE
![npm config set registry not working npm config set registry not working](https://user-images.githubusercontent.com/21073295/27952992-865dff8e-630a-11e7-80ee-bfcba1e0890b.png)
Other ( see below for feature requests):.npm is doing something I don't understand.