`ionic start` command throws npm 404 error when the global npm config has a private registry
See original GitHub issueDescription:
I cannot create a new ionic application with ionic start
command
Steps to Reproduce:
- Create a ~/.npmrc file with your custom npm registry. For example:
registry=https://mycompany.com/npm/
- Run
ionic start --pro-id <app_id>
command
Output:
NPM throws 404 error
I guess to solve the issue the cli should add --registry <path-to-global-registry>
parameter when installing dependencies.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Installing npm package fails with 404 - node.js - Stack Overflow
Try first this commands (in windows run as administrator) npm config set registry http://registry.npmjs.org npm install -g @angular/cli.
Read more >Surviving the npm ERR! 404 with private packages
Private packages are npm packages that are not accessible to everyone, but only to members of a specific organization that have access ...
Read more >(Solved) npm ERR! code E404 while working with Power ...
Solution ; STEP 1 : run below commands to solve this issue. npm config set registry http://registry.npmjs.org ; STEP 2 : run below...
Read more >try creating one first with: npm i --package-lock-only - You.com
This issue exists in the latest npm version. I am using the latest npm; Current Behavior. Using npm install --global <pack> can suggest...
Read more >firebase-admin - npm
Firebase admin SDK for Node.js. Latest version: 11.4.1, last published: 4 days ago. Start using firebase-admin in your project by running ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@dmitryshimkin I think that’s the best workaround for now. If this issue gets more attention, we’ll revisit. Is that fair?
I just learnt that npm config properties can be set via environment variables. So there is a workaround for such case: