Yarn: Some packages may be 404ing

Created on 6 Aug 2020  ·  55Comments  ·  Source: yarnpkg/yarn

I don't know if this issue is wider than just one package, but visiting

https://registry.yarnpkg.com/@gooddata/gooddata-js/-/gooddata-js-11.19.1.tgz

is 404ing. Visiting npm registry on the other hand resolves:

https://registry.npmjs.org/@gooddata/gooddata-js/-/gooddata-js-11.19.1.tgz

Most helpful comment

"Decentralization is a key", they told us.. "Don't put your eggs in one basket".. And here we go. One thing broke and we are reading comments instead of working.

All 55 comments

It is. getting this on multiple packages:
https://registry.yarnpkg.com/@codler/react-native-keyboard-aware-scroll-view/-/react-native-keyboard-aware-scroll-view-1.0.0.tgz
https://registry.yarnpkg.com/@react-native-community/cameraroll/-/cameraroll-1.8.1.tgz

Can confirm multiple packages are impacted.

Confirm - @vuepress/core@^1.3.1

Confirmed!! 404, and 503 both meet

It seems random, any package is possible to be 404 or 503.

Yea i have the same problem

404 error https://registry.yarnpkg.com/@fortawesome/free-brands-svg-icons/-/free-brands-svg-icons-5.12.1.tgz

Looks like an incident with npm https://status.npmjs.org, specifically scoped packages.

It took me a while to figure out isn't it a joke

Screenshot 2020-08-06 at 11 19 34

https://status.yarnpkg.com/ isn't happy either

@strongpauly I _think_ that page has been gone for a while now, as in it's no longer active.

Same with package like https://registry.yarnpkg.com/@simonwep/pickr and css-diff.
Error is either 404 or 503

registry.yarnpkg.com is only a DNS redirection as stated in https://twitter.com/yarnpkg/status/1088356674539270146

Issue comes from NPM, as their status page shows : https://status.npmjs.org/

+1

+1 https://registry.yarnpkg.com/@jest/core/-/core-24.9.0.tgz and a bunch of other packages

@material-ui too

@loadable/component
@sentry/browser

Affected for me.

+

registry.yarnpkg.com is only a DNS redirection as stated in https://twitter.com/yarnpkg/status/1088356674539270146

Issue comes from NPM, as their status page shows : https://status.npmjs.org/

Do we really need to list all scoped package ? or can we read the comments ?

"Decentralization is a key", they told us.. "Don't put your eggs in one basket".. And here we go. One thing broke and we are reading comments instead of working.

the same for emotion and vue-emotion packages
this is the copy of yarn-error.log file both packaged present in yarn and npm registries
Arguments:
/usr/bin/node /usr/share/yarn/bin/yarn.js add @egoist/vue-emotion

PATH:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

Yarn version:
1.22.4

Node version:
12.18.3

Platform:
linux x64

Trace:
Error: https://registry.yarnpkg.com/@egoist%2fvue-emotion: Not found
at Request.params.callback [as _callback] (/usr/share/yarn/lib/cli.js:66987:18)
at Request.self.callback (/usr/share/yarn/lib/cli.js:140748:22)
at Request.emit (events.js:315:20)
at Request. (/usr/share/yarn/lib/cli.js:141720:10)
at Request.emit (events.js:315:20)
at IncomingMessage. (/usr/share/yarn/lib/cli.js:141642:12)
at Object.onceWrapper (events.js:421:28)
at IncomingMessage.emit (events.js:327:22)
at endReadableNT (_stream_readable.js:1220:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)

npm manifest:
{
"name": "test-emotion",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"author": "",
"license": "ISC"
}

yarn manifest:
No manifest

Lockfile:
No lockfile

+1

+1
error An unexpected error occurred: "https://registry.yarnpkg.com/@emotion/cache/-/cache-10.0.29.tgz: Request failed \"404 Not Found\"".

The registry https://replicate.npmjs.com/ (yarn install --registry https://replicate.npmjs.com/ or yarn config set registry https://replicate.npmjs.com/) seems to cause less trouble.

The registry https://replicate.npmjs.com/ (yarn install --registry https://replicate.npmjs.com/) seems to cause less trouble.

RIP replicate.npmjs.com inbox 😆

Getting this error still for ;
error An unexpected error occurred: "https://registry.yarnpkg.com/@rails/webpacker/-/webpacker-4.2.2.tgz: Request failed \"404 Not Found\"".
Also @rails/actioncable
@popperjs/core
@rails/activestorage
intermittently

404 not found +1 for me. I see that the corresponding plug-in is marked as invalid for npm on github

cannot install plugin too
@babel/plugin-transform-react-display-name

It is useless to comment with +1s or packages exemples as the issue is random on all scoped packages, it only makes it harder for newcomers to find the cause.

在线等 挺急的

I noticed that only packages starting with @ are causing this error.

I guess it is because of NPM issues:

https://status.npmjs.org/incidents/cksjqc1w11v5

Issues accessing npmjs.com and installing scoped packages

image

Thx @RyuuGan it as been told many time before, you can just read the previous comments

Any update?

https://registry.yarnpkg.com/@rollup/plugin-replace/-/plugin-replace-2.3.3.tgz: Request failed \"404 Not Found\""

Same - getting errors on multiple packages

the same, from https://registry.yarnpkg.com/@typescript-eslint/experimental-utils/-/experimental-utils-2.12.0.tgz

Same on multiple Packages

Facing the same issue for all the packages

Same, right now I'm not able to install any package.

What the hell is going on with your crappy servers? Cant even install yarn itself!

Сейчас зафиксят, не кипишуйте. 😄

What the hell is going on with your crappy servers? Cant even install yarn itself!

Never really had issiues with NPM no need to be so hostile. I'm sure it was not intentional and they're doing the best they can. As if you never had a bug in your system...

https://status.npmjs.org/incidents/cksjqc1w11v5

You can keep track the Specific Incident Status here

I'm facing same issues with multiple packages - 404 not found

Try to use the Open-registry while waiting for the NPM one to work properly again:

# To start using Open-Registry
# Replace "npm" with your client (such as "yarn")
npm config set registry https://npm.open-registry.dev

# To stop using Open-Registry
# Replace "npm" with your client
npm config delete registry

https://open-registry.dev/

yarn add v1.22.4
[1/4] Resolving packages...
[2/4] Fetching packages...
info [email protected]: The platform "win32" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "win32" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "react-scripts > @typescript-eslint/eslint-plugin > [email protected]" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 24 new dependencies.
info Direct dependencies
├─ @material-ui/[email protected]
├─ [email protected]
└─ [email protected]
info All dependencies
├─ @babel/[email protected]
├─ @emotion/[email protected]
├─ @material-ui/[email protected]
├─ @material-ui/[email protected]
├─ @material-ui/[email protected]
├─ @types/[email protected]
├─ @types/[email protected]
├─ @types/[email protected]
Compiled successfully!

is up again! at least in material ui

npm install -g yrm

try other registry

yrm ls

  npm ---- https://registry.npmjs.org/
  cnpm --- http://r.cnpmjs.org/
* taobao - https://registry.npm.taobao.org/
  nj ----- https://registry.nodejitsu.com/
  rednpm - http://registry.mirror.cqupt.edu.cn/
  npmMirror  https://skimdb.npmjs.com/registry/
  edunpm - http://registry.enpmjs.org/
  yarn --- https://registry.yarnpkg.com

It worked just now for me, maybe yours too

"We replaced the faulty cache and our telemetry indicates a significant improvement in error rates. We'll continue to monitor the situation and make sure all issues are fully resolved.
Posted 3 minutes ago. Aug 06, 2020 - 11:36 UTC"

From the NPM issue
https://status.npmjs.org/incidents/cksjqc1w11v5

works

Status: Resolved. Please close and lock this ticket.

Was this page helpful?
0 / 5 - 0 ratings