[BUG] npm i failing for random packages on retry saying package not found

[manojbavikati]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

npm ERR! 404 Not Found - GET https://registry.npmjs.org/@antv%2fl7-component - Not found

Expected Behavior

install should complete without errors.

Steps To Reproduce

1. In this environment...
2. With this config...
3. Run '...'
4. See error...

Environment

• npm:9.6.7
• Node.js:v18.16.1
• OS Name: Windows 11
• System Model Name:
• npm config:

; copy and paste output from `npm config ls` here

[jfirebaugh]

Also seeing this. Looks like consistency issues with the CDN or something like that.

[jfirebaugh]

Repeat of #1626?

[codybswaney]

Also seeing this, inconsistency with pulling various packages over the last 45+ minutes or so.

The full error from the first package we saw it on:

#10 79.31 npm ERR! code E404
#10 79.31 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@vercel%2fncc - Not found
#10 79.31 npm ERR! 404 
#10 79.31 npm ERR! 404  '@vercel/ncc@0.34.0' is not in this registry.
#10 79.31 npm ERR! 404 
#10 79.31 npm ERR! 404 Note that you can also install from a
#10 79.31 npm ERR! 404 tarball, folder, http url, or git url.
#10 79.32 
#10 79.32 npm ERR! A complete log of this run can be found in:
#10 79.32 npm ERR!     /root/.npm/_logs/2023-07-14T19_49_53_940Z-debug-0.log
#10 ERROR: process "/bin/sh -c npm ci" did not complete successfully: exit code: 1

For clarity, @vercel/ncc@0.34.0 does exist.

[iagormoraes]

Also seeing this, inconsistency with pulling various packages over the last 45+ minutes or so.

The full error from the first package we saw it on:

#10 79.31 npm ERR! code E404
#10 79.31 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@vercel%2fncc - Not found
#10 79.31 npm ERR! 404 
#10 79.31 npm ERR! 404  '@vercel/ncc@0.34.0' is not in this registry.
#10 79.31 npm ERR! 404 
#10 79.31 npm ERR! 404 Note that you can also install from a
#10 79.31 npm ERR! 404 tarball, folder, http url, or git url.
#10 79.32 
#10 79.32 npm ERR! A complete log of this run can be found in:
#10 79.32 npm ERR!     /root/.npm/_logs/2023-07-14T19_49_53_940Z-debug-0.log
#10 ERROR: process "/bin/sh -c npm ci" did not complete successfully: exit code: 1

For clarity, @vercel/ncc@0.34.0 does exist.

Is not only this package, various others is happening the same.

[JavaScriptBach]

Most likely the NPM registry is busted. Still no incident declared in https://status.npmjs.org/ sadly

[codybswaney]

Yes, thanks @iagormoraes I should have clarified better: we are seeing it happening on various packages and it's very inconsistent. E.g. my last build failed on another package:

npm ERR! 404 Not Found - GET https://registry.npmjs.org/@graphql-tools%2fdelegate - Not found
npm ERR! 404 
npm ERR! 404  '@graphql-tools/delegate@9.0.21' is not in this registry.

[melMass]

Same here, it worked on the node-setup github action by explicitely telling it the registry url, but our docker build now trigger the same

[manojbavikati]

Looks like the npm registry issue is resolved for me after multiple retry. Looks like it was failing for random packages

[Konard]

We had a problem for https://registry.npmjs.org/@tand_ferret%2fuseful_hooks too for a short period of time after publish. So this issue continue to reproduce.

deep-foundation/npm-packager#97 - our issue on that problem.