Installing npm package fails with 404

Question

Using the command prompt, I am trying to install angular CLI and it fails. I have npm version 5.5.1 and node version v8.9.1. I am trying to install angular cli using the command

npm install -g @angular/cli@latest

and it fails with the error:

npm ERR! code E404 npm ERR! 404 Not Found: @angular/cli@latest npm ERR! A complete log of this run can be found in:

I look at the log file and I see its trying to fetch the package from a location that doesn't exist. Not sure from where it gets pulled. How do I fix this location path and install angular cli. Same happens when I try to install typescript or any other npm package. all of them try to install from the location mentioned below and it fails with 404

8 http fetch GET 404 
       http://nuget.feed.xyz.corp:8729/npm/FeedNPM/@angular%2fcli 109ms
9 silly fetchPackageMetaData error for @angular/cli@latest 404 Not Found: 
     @angular/cli@latest
10 verbose stack Error: 404 Not Found: @angular/cli@latest

What's your question? It looks like @angular/cli doesn't exist. — EvSunWoodard
– EvSunWoodard, Commented Nov 27, 2017 at 21:37
See this question's top answer, and use the default npm registry location: stackoverflow.com/questions/22385092/… . Registry: registry.npmjs.org — EvSunWoodard
– EvSunWoodard, Commented Nov 27, 2017 at 21:51
Yep, That was it. Can't thank you enough!! Your answer made my day! — theandroid
– theandroid, Commented Nov 27, 2017 at 22:08

Community · Accepted Answer · 2018-12-18 23:03:11Z

98

npm config set registry http://registry.npmjs.org

NPM registry documentation

edited Dec 18, 2018 at 23:03

CommunityBot

11 silver badge

answered Nov 27, 2017 at 23:36

Matt

1,2068 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

nitrex Over a year ago

Should be the accepted answer - Weird took me a while to find through searches thanks

Mark Over a year ago

Should I use http or https?

ranbuch Over a year ago

Looks lie it's redirecting to https so it doesn't matter

starbeamrainbowlabs Aug 20 at 12:03

It doesn't redirect to HTTP for me - showing a 426 upgrade required in the terminal -and this does not fix the issue.

Atul Baldaniya · Accepted Answer · 2020-08-06 11:36:56Z

23

Try first this commands (in windows run as administrator)

npm config set registry http://registry.npmjs.org
npm install -g @angular/cli

if still not working let's update NPM and nodejs by running this commands

npm -g install npm
npm cache clean -f
npm install -g n

then try to run

npm install -g @angular/cli

This should solve this problem

answered Aug 6, 2020 at 11:36

Atul Baldaniya

8999 silver badges14 bronze badges

2 Comments

Cheolsoon Im Over a year ago

When I do the above options, I got rollbackFailedOptional and ETIMEOUT later. Any advice will be greatly appreciated.

Atul Baldaniya Over a year ago

in which OS? if you are using windows just then you can try to unintall and try again may be this works.

Alexus · Accepted Answer · 2019-02-03 19:14:00Z

16

in my case it was .npmrc file in my project dir, which kept overwriting my global registry url. As soon as I deleted it, I could finally use npm install

answered Feb 3, 2019 at 19:14

Alexus

1,9623 gold badges26 silver badges54 bronze badges

2 Comments

codeinprogress Over a year ago

Same here. Had to delete .npmrc (was trying to install private package) , then do npm install and once it worked I restored the .npmrc back to the project

Sanke Over a year ago

I had an issue with my .npmrc file. There were some mandatory entries that I had missed.

nick · Accepted Answer · 2020-08-05 09:52:34Z

6

Add a .npmrc file in the root of the project. .npmrc will look like below -

@xy:registry=https://xyz.jfrog.io/xyz/api/npm/npm-local/ @xy-app:registry=https://xyz.jfrog.io/xyz/api/npm/npm-local/

And Delete all the field eg - email , auth etc. Find out what is the registry url of your application and put it into the registry.

Then run command - npm install And it will work.

edited Aug 5, 2020 at 9:52

answered Aug 5, 2020 at 9:25

nick

4754 silver badges14 bronze badges

Comments

Abhay · Accepted Answer · 2019-09-23 16:52:41Z

4

It was giving the same error for me when I use office network/vpn as they have 'umbrella' DNS security shield. To solve this issue, connect to personal network and type the below commands:

    npm config set registry http://registry.npmjs.org
    npm install -g @angular/cli

answered Sep 23, 2019 at 16:52

Abhay

3112 silver badges4 bronze badges

Comments

Harry Riley · Accepted Answer · 2022-07-04 16:01:26Z

4

I spent hours on this.

I had to follow the below steps to get it to work (mac).

Delete my LOCAL (not project) .npmrc by running:

rm /Users/<NAME>/.npmrc

Then set the registry:

npm config set registry https://registry.npmjs.org/

Then follow the steps for logging in to npm:

npm login

Check what's in your config list by running:

npm config list

It should look like this:

//registry.npmjs.org/:_authToken = (protected)
registry = "https://registry.npmjs.org/"

Hope it works for you too.

answered Jul 4, 2022 at 16:01

Harry Riley

3433 silver badges10 bronze badges

Comments

Agent · Accepted Answer · 2019-09-26 15:03:53Z

3

Alternative, another option to avoid 404 npm error

check if your terminal is in the root directory, if not your npm scripts will not execute because it will not be able to see the package.json

answered Sep 26, 2019 at 15:03

Agent

1,39518 silver badges22 bronze badges

Comments

Parking Master · Accepted Answer · 2023-05-17 17:12:30Z

3

When I looked for .npmrc in home folder I couldn’t find it.

But and after running:

$ npm config set registry http://registry.npmjs.org

This fixed my problem.

edited May 17, 2023 at 17:12

Parking Master

6571 gold badge10 silver badges26 bronze badges

answered May 15, 2023 at 10:39

Abdelellah Dandashi

1071 gold badge2 silver badges8 bronze badges

Comments

Cabezas · Accepted Answer · 2020-06-24 15:11:45Z

2

I had same problem with a private package. Need to:

npm adduser
npm login

edited Jun 24, 2020 at 15:11

Cabezas

10.9k9 gold badges73 silver badges72 bronze badges

answered May 28, 2019 at 8:40

Ronen

8371 gold badge13 silver badges35 bronze badges

Comments

Ndiklas · Accepted Answer · 2022-06-05 16:38:28Z

1

Uninstall NPM & nodejs and install the right way NPM (Ubuntu)

sudo with npm is not recommended

To Uninstall

sudo apt-get remove nodejs
sudo apt-get remove npm

or

sudo apt-get purge nodejs

Followed by proper installation

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash

To confirm open a new terminal run:

$ command -v nvm

Latest LTS release of NodeJS:

$ nvm install --lts

Set default environment

$ nvm alias default lts/*

edited Jun 5, 2022 at 16:38

answered Jun 5, 2022 at 16:26

Ndiklas

871 silver badge6 bronze badges

Comments

IlGala · Accepted Answer · 2019-10-04 07:22:41Z

0

change your access level to public. type this in the terminal

npm --access=public

install your angular.

sudo npm install @ngular/cli

edited Oct 4, 2019 at 7:22

IlGala

3,4494 gold badges42 silver badges53 bronze badges

answered Oct 4, 2019 at 2:56

solomon tekie

11 bronze badge

Comments

NOZUONOHIGH · Accepted Answer · 2020-07-14 09:22:38Z

0

In my case, that's a typo error:
change trct-js-sdk to trtc-js-sdk saved my life.

answered Jul 14, 2020 at 9:22

NOZUONOHIGH

2,0241 gold badge25 silver badges22 bronze badges

Comments

Puneet Lamba · Accepted Answer · 2022-04-08 00:52:46Z

0

My solution was as follows because I had a dependency on a private package. If you see the dependency in package.json defined in the format @scope/package, then @scope tells you that it's a scoped package that might be private.

Get the private package owner to grant you access to the package
Upgrade npm
Upgrade node
Add registry using HTTPS (not HTTP), e.g. npm config set registry https://registry.npmjs.org
Do "npm login"
Now run the build

answered Apr 8, 2022 at 0:52

Puneet Lamba

7891 gold badge8 silver badges15 bronze badges

Comments

Lee Taylor · Accepted Answer · 2022-06-10 14:40:31Z

0

Worked for me

I got

error 404 'dotnev@*' is not in this registry.

Deleted .npmrc file in 2 folders back over my project root and then in the project root folder typed:

npm i dotenv

copied from: https://www.npmjs.com/package/dotenv

edited Jun 10, 2022 at 14:40

Lee Taylor

7,99416 gold badges38 silver badges53 bronze badges

answered Jun 5, 2022 at 4:43

Shamir

11 bronze badge

Comments

Hamdollah Hoseinpour · Accepted Answer · 2023-02-06 20:45:43Z

0

Just run sudo npm config set registry http://registry.npmjs.org and then update your npm.

answered Feb 6, 2023 at 20:45

Hamdollah Hoseinpour

1

Comments

Tyler2P · Accepted Answer · 2023-05-03 18:41:06Z

0

I had the same problem. What did I do?

First I deleted the .npmrc file in home/user

ls -a
sudo rm .npmrc

Then I downgraded my npm to a lower version

npm install -g [email protected]

Then in my application I deleted the node_module package and runned the npm install.

edited May 3, 2023 at 18:41

Tyler2P

2,37030 gold badges26 silver badges34 bronze badges

answered May 2, 2023 at 21:42

Marcos Silva

1

Comments

thisisB · Accepted Answer · 2023-11-14 12:34:54Z

0

The top most answer is correct and will solve your issue with 404 error. Just wanted to add to this answer that helped me resolve the issue in my case.

Post setting the registry,

Do a npm cache clean and restart your system. Now, try re-installing the package, it should work.

answered Nov 14, 2023 at 12:34

thisisB

112 bronze badges

1 Comment

Aaron Meese Over a year ago

This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review

user26483682 · Accepted Answer · 2024-07-23 11:38:44Z

0

if private repo running behind reverse proxy server, and using proxypass to redirect request from apache to nexus repo. then special character in url may be because of Encoding of slash on apache server.

set below parameter to fix on apache.

AllowEncodedSlashes NoDecode

answered Jul 23, 2024 at 11:38

user26483682

1

Comments

Mark · Accepted Answer · 2024-12-08 19:07:52Z

0

Verify that the npm is pointing in the correct place:

npm config get registry

my mistake is that it was pointing to "http" not "https"

so just reset the config:

npm config set registry https://registry.npmjs.org/

answered Dec 8, 2024 at 19:07

Mark

111 silver badge3 bronze badges

Comments

kajal · Accepted Answer · 2020-03-06 11:20:27Z

-2

It is an network error , check your network connection and try to install it again.

answered Mar 6, 2020 at 11:20

kajal

1

Comments

Hassan Braim · Accepted Answer · 2020-09-23 12:31:33Z

-2

the only command line "npm -g install npm" solved the issue for me! the following link can be helpful to dig deep for a better understanding. Thanks a lot.

answered Sep 23, 2020 at 12:31

Hassan Braim

71 silver badge

1 Comment

Taslim Oseni Over a year ago

"The following link"? Where?

Collectives™ on Stack Overflow

Installing npm package fails with 404

21 Answers 21

4 Comments

2 Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

21 Answers 21

4 Comments

2 Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related