An unexpected error occurred: "https://registry.yarnpkg.com/<package>: Not found" #5865

IlCallo · 2018-05-24T08:56:30Z

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
I cannot install some packages globally when in Windows and using Git Bash.
For example, for @nrwl/schematics (but also for @angular/cli) I get

$ yarn global add @nrwl/schematics
yarn global v1.7.0
[1/4] Resolving packages...
error An unexpected error occurred: "https://https://registry.yarnpkg.com/@nrwl/schematics: Not found".

Error log:

  Error: https://registry.yarnpkg.com/@nrwl/schematics: Not found
      at Request.params.callback [as _callback] (C:\Program Files (x86)\Yarn\lib\cli.js:65656:18)
      at Request.self.callback (C:\Program Files (x86)\Yarn\lib\cli.js:134675:22)
      at Request.emit (events.js:159:13)
      at Request.<anonymous> (C:\Program Files (x86)\Yarn\lib\cli.js:135658:10)
      at Request.emit (events.js:159:13)
      at IncomingMessage.<anonymous> (C:\Program Files (x86)\Yarn\lib\cli.js:135578:12)
      at Object.onceWrapper (events.js:254:19)
      at IncomingMessage.emit (events.js:164:20)
      at endReadableNT (_stream_readable.js:1062:12)
      at process._tickCallback (internal/process/next_tick.js:152:19)

In Ubuntu it seems to work just fine.
Same if I use the Windows PowerShell instead of Git Bash.

If the current behavior is a bug, please provide the steps to reproduce.
See above

What is the expected behavior?
That packages are installed

Please mention your node.js, yarn and operating system version.

$ node -v
v9.3.0

$ yarn config list
yarn config v1.7.0
info yarn config
{ 'version-tag-prefix': 'v',
  'version-git-tag': true,
  'version-commit-hooks': true,
  'version-git-sign': false,
  'version-git-message': 'v%s',
  'init-version': '1.0.0',
  'init-license': 'MIT',
  'save-prefix': '^',
  'bin-links': true,
  'ignore-scripts': false,
  'ignore-optional': false,
  registry: 'https://registry.yarnpkg.com',
  'strict-ssl': true,
  'user-agent': 'yarn/1.7.0 npm/? node/v9.3.0 win32 x64',
  lastUpdateCheck: 1527149439512 }
info npm config
{}

Windows 10

The text was updated successfully, but these errors were encountered:

bkad · 2018-05-31T18:54:17Z

Getting the same error message, but maybe a different cause?

$ docker run --rm node:10 yarn global add @types/graphql@0.12.4

yarn global v1.7.0
[1/4] Resolving packages...
(node:1) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@types/graphql/-/graphql-0.12.4.tgz: Request failed \"404 Not Found\"".

IlCallo · 2018-05-31T19:04:23Z

Yeah, seems a different one. Mine seems to be triggered by the usage of Git Bash and its strange behaviour around the "/" character on Windows.

Today I noticed that now it doesn't install any package with a namespace, probably because it converts "/" to backslash for some obscure reasons...

Jasu · 2018-06-04T10:55:19Z

This seems to happen randomly - if I run curl repeatedly, the following works around 10% of the time:

curl 'https://registry.yarnpkg.com/@types/node/-/node-9.4.2.tgz'

chiel · 2018-06-06T09:22:06Z

Getting the same issue during our CI build, always fails on the same url @Jasu posted. Indeed it seems to happen randomly so I don't think changing yarn client version or anything will happen. Almost seems like there's a caching layer in place that has cached a 404 on some of its nodes or something.

sgraham785 · 2018-06-06T21:26:01Z

Having the same failure as @Jasu is seeing, which just started occurring today. Looks like it could have been cache that allowed it to work 10% of the time, but that seems to have been purged now and I have yet to download it.

seems that the referenced types package at https://registry.npmjs.org/@types/node/-/node-9.4.2.tgz is gone, even though it's still referenced in https://registry. yarnpkg.org/@types/node -> versions.9.4.2.dist.tarball

Anyone on the yarn team aware of why this is removed?

seems that node-9.6.0+ is available, however upgrading to yarn 1.7.0, ~~using node 10 it still tries to pull the node-9.4.3 types tarball~~ has no affect on this and is most likely from a dep (such as in my case)

will try updating the types dep and report back

sgraham785 · 2018-06-06T22:05:54Z

yep upgrading my @types/node dep to 9.6.0 worked. not ideal but worked.

i think it's important to mention that this is not a yarn only issue as I found the same issue using npm only and discovered that the @types/9.4.2 & 9.4.3 tarballs missing from the interwebs which could be something to do with removal of those packages by DefinitelyTyped or storage issue on npmjs.org, I wasn't able to find much other info regarding this issue which is why i am adding the context

anied · 2018-06-12T15:28:01Z

Hey all, heads up-- Had this same issue on mac and was able to resolve this with the following steps:

Upgraded to latest yarn version (might not actually be necessary, but wanted to note it was a step I took)
remove node_modules
remove yarn.lock
yarn install

And everything worked/installed as expected.

My hunch is that the salient step is the removal of yarn.lock.

vinujosef · 2018-06-13T06:17:32Z

@anied I also have the similar issue, but when I remove yarn.lock -> it shows "No lockfile found" and quits the process.

Ranhiru · 2018-06-20T07:14:44Z

After upgrading from Yarn 1.6.0 to 1.7.0 I just deleted the lock file and ran yarn install. Then my yarn add commands started running again without any issue

peterlavey · 2018-09-01T14:20:34Z

First

npm install

and then...

yarn

jamsheedpk · 2018-10-16T08:05:09Z

Arguments:
/usr/local/bin/node /usr/bin/yarn add react-native-modelbox

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

Yarn version:
1.7.0

Node version:
10.4.1

Platform:
linux x64

Trace:
Error: https://registry.yarnpkg.com/react-native-modelbox: Not found
at Request.params.callback [as _callback] (/usr/lib/node_modules/yarn/lib/cli.js:65656:18)
at Request.self.callback (/usr/lib/node_modules/yarn/lib/cli.js:134675:22)
at Request.emit (events.js:182:13)
at Request. (/usr/lib/node_modules/yarn/lib/cli.js:135658:10)
at Request.emit (events.js:182:13)
at IncomingMessage. (/usr/lib/node_modules/yarn/lib/cli.js:135578:12)
at Object.onceWrapper (events.js:273:13)
at IncomingMessage.emit (events.js:187:15)
at endReadableNT (_stream_readable.js:1081:12)
at process._tickCallback (internal/process/next_tick.js:63:19)

jimklo · 2019-05-02T22:41:19Z

Similar issue:

> npx create-react-app --info

Environment Info:

  System:
    OS: macOS 10.14.4
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  Binaries:
    Node: 12.1.0 - /usr/local/bin/node
    Yarn: 1.15.2 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 73.0.3683.103
    Firefox: Not Found
    Safari: 12.1
  npmPackages:
    react: Not Found
    react-dom: Not Found
    react-scripts: Not Found
  npmGlobalPackages:
    create-react-app: Not Found

> npx create-react-app my-app

Creating a new React app in /Users/jklo/projects/jnwc/source/my-app.

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts...

yarn add v1.15.2
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@csstools/normalize.css/-/normalize.css-9.0.1.tgz: Request failed \"404 Not Found\"".
info If you think this is a bug, please open a bug report with the information provided in "/Users/jklo/projects/jnwc/source/my-app/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Aborting installation.
  yarnpkg add --exact react react-dom react-scripts --cwd /Users/jklo/projects/jnwc/source/my-app has failed.

Deleting generated file... package.json
Deleting generated file... yarn.lock
Done.

yarn-error.log

Curl can download the package without any problems. ~~Cannot seem to figure out how to even work around this.~~

edit: I determined the problem... this is certainly terrible error messaging by yarn or npm (not sure if yarn reimplements npm's features or not). Turns out in my instance, I had some bad authentication credentials in my ~/.npmrc, that once removed, allowed scoped packages to download again. I'm still a bit confused by my observation to why this was only a problem for some packages, specifically scoped packages.

jaapaurelio · 2019-05-10T06:16:57Z

Had the same problem. I changed my ~/.npmrc to add always-auth = false. It's working now.

MartinYounghoonKim · 2019-05-20T02:20:46Z

@jaapaurelio
I add it, but doesnt' work. Do u have any solution?

Stoobaart · 2019-06-05T10:03:52Z

Running the below command in terminal fixed my issue:

yarn config set strict-ssl false

IlCallo · 2019-06-10T08:16:22Z

I don't know what that config option does, but given the name it doesn't seem a good idea to set it to false randomly...
Can you explain why you did it and what is it supposed to do?

Stoobaart · 2019-06-10T08:38:14Z

Hiya, for me it was causing problems due to my strict secure corporate network. It just allowed me to bypass that. I'd just make sure you know what packages you're installing first, and then flip it back to true afterwards. But I'm far from an expert in this, so if anyone has any insights as to any possible dangers here, I'd love to read about them. Cheers everyone.

vabole · 2019-08-15T09:58:40Z

Had this error with sinon:

from packge.json:
"sinon": "^7.0.0",

Error in terminal:
error An unexpected error occurred: "https://registry.yarnpkg.com/sinon/-/sinon-7.4.0.tgz: Request failed \"404 Not Found\"".

I was able to resolve it with:
yarn upgrade --latest sinon

Which made yarn look for sinon-7.4.1.tgz instead.

gilmoreorless · 2019-10-01T07:00:08Z

Our builds have been failing intermittently with this same error for the last couple of days. The first failure we noticed was at 2019-09-30T00:01 UTC.

The failures are happening fairly frequently (but not every time, more like 80-90% of the time). It's always the same error, but for 4 different packages so far:

Each of these packages is public, and each version that's failing is the latest one published, so upgrading to a newer version isn't an option. Doing a curl request directly from one of the build machines returns a 200 OK response.

The various suggestions above (and in many other issues) to delete yarn.lock and re-install the modules aren't going to work, because that completely defeats the point of using a lockfile in the first place. Doing so will upgrade every single transitive dependency, instead of actually fixing what is clearly an intermittent problem with the registry itself.

knoxcard · 2019-10-02T20:20:26Z

root@TRON:/mnt/c/indospace.io/services# yarn upgrade --latest
yarn upgrade v1.19.0
warning package.json: No license field
error No lockfile in this directory. Run `yarn install` to generate one.
info Visit https://yarnpkg.com/en/docs/cli/upgrade for documentation about this command.
root@TRON:/mnt/c/indospace.io/services# yarn install
yarn install v1.19.0
warning package.json: No license field
info No lockfile found.
warning No license field
[1/5] Resolving packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/binlookup: getaddrinfo EAI_AGAIN registry.yarnpkg.com".
info If you think this is a bug, please open a bug report with the information provided in "/mnt/c/indospace.io/services/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
root@TRON:/mnt/c/indospace.io/services#

I concur, the yarn registry is completely screwed up at the moment. Never seen it this bad on my side...keep getting these networks errors. I've deleted yarn lock and tried a ton of solutions that used to work for me in the past....don't know what to do.

knoxcard · 2019-10-02T20:56:02Z

Problem Solved! Not a yarn problem, but rather a Windows Subsystem for Linux (WSL): connectivity issue.

RyanPWalker · 2019-10-07T23:01:54Z

Oddly enough, I just needed to restart my computer. The good ol' turn it off and on again. I tried several different things including the above solutions, but restarting did the trick.

bobysf12 · 2019-12-05T00:13:22Z

Problem Solved! Not a yarn problem, but rather a Windows Subsystem for Linux (WSL): connectivity issue.

I'm having the same problem. I'm using WSL too. Could you share how did you solve it? 😄

lirbank · 2019-12-20T17:40:17Z

I'm on macOS, and like @RyanPWalker I just rebooted and the error was gone.

coYms · 2019-12-30T09:38:05Z

I just delete the yarn.lock file and try yarn add again, It worked !

doug31415 · 2020-02-12T15:39:23Z

Getting this:

error An unexpected error occurred: "https://registry.yarnpkg.com/7zip-bin: Not found".

deleting yarn.lock and node_modules and then reinstalling hasnt worked, we dont use WSL. Might be related to
https://stackoverflow.com/questions/60185963/error-when-i-run-npm-install-error-404-not-found-7zip-bin4-1-0,
but the post claims the issues there are fixed

This looks like a problem with yarn. Any thoughts?

kaitlynbrown · 2020-02-12T18:39:53Z

I'm seeing this error now when trying to run builds on CodeBuild:

error An unexpected error occurred: "https://registry.yarnpkg.com/error-ex/-/error-ex-1.3.2.tgz: Request failed \"404 Not Found\"".

RabeeAbuBaker-Exalt · 2020-08-06T11:35:36Z

After breaking the build on production level... it's back working now

RabeeAbuBaker-Exalt · 2020-08-06T11:39:46Z

Another update:

Update - 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.
Aug 6, 11:36 UTC

NPM Status

bipindubey-technoark · 2020-08-06T11:39:50Z

Its working now Thanks

LevanSanadiradze · 2020-08-06T11:39:53Z

It worked for me, even though the npm status page still shows partial outage.

khurram-wasim · 2020-08-06T11:40:37Z

A sight of relief !

anthonyminyungi · 2020-08-06T11:41:00Z

Thank you npm :)

RabeeAbuBaker-Exalt · 2020-08-06T11:41:30Z

🎉🎉🎉🎉

shinjiber · 2020-08-06T11:42:17Z

thank you npm always

osamaeshtiaq · 2020-08-06T12:14:33Z

Working fine now!

nvtin · 2020-08-06T12:34:34Z

Working now. Thanks!

kamranblueeast · 2020-08-06T12:46:45Z

Working now...:)

minhhy2801 · 2020-08-07T02:41:18Z

Yarn version: 
  1.22.4

Node version: 
  12.16.2

Platform: 
  win32 x64

Trace: 
  Error: https://registry.npmjs.org/@material-ui%2fcore/i18next: Request "https://registry.npmjs.org/@material-ui%2fcore/i18next" returned a 405
      at Request.params.callback [as _callback] (C:\Program Files (x86)\Yarn\lib\cli.js:66105:18)
      at Request.self.callback (C:\Program Files (x86)\Yarn\lib\cli.js:140748:22)
      at Request.emit (events.js:310:20)
      at Request.<anonymous> (C:\Program Files (x86)\Yarn\lib\cli.js:141720:10)
      at Request.emit (events.js:310:20)
      at IncomingMessage.<anonymous> (C:\Program Files (x86)\Yarn\lib\cli.js:141642:12)
      at Object.onceWrapper (events.js:416:28)
      at IncomingMessage.emit (events.js:322:22)
      at endReadableNT (_stream_readable.js:1187:12)
      at processTicksAndRejections (internal/process/task_queues.js:84:21)

Still happens with me

wadamomo · 2020-08-15T01:15:15Z

yarn config set registry https://registry.npmjs.org
rm yarn.lock
yarn

worked for me

Pintot · 2020-08-16T18:27:27Z

Had the same issue here, and working none of the solutions! My goshi

Pintot · 2020-08-16T18:30:42Z

Is not working guys!

$ yarn add react-route-dom
yarn add v1.22.4
[1/4] Resolving packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/react-route-dom: Not found".
info If you think this is a bug, please open a bug report with the information provided in "C:\wamp64\www\myapp\y
arn-error.log".

yael-screenovate · 2020-08-23T19:13:49Z

same issue by me:(
error An unexpected error occurred: "https://registry.yarnpkg.com/jspfd: Not found".
nothing from above helped.

GitHubAjit · 2020-09-06T08:07:07Z

run
yarn config set registry https://registry.npmjs.org
will do the job

andreapiras · 2020-09-15T14:30:06Z

I was using my phone as hotspot. Restarting the phone fixed the issue 🤷

pak11273 · 2020-09-22T15:13:42Z

run
yarn config set registry https://registry.npmjs.org
will do the job

Doesn't work for me

mayooresan · 2020-09-28T02:18:43Z

If you are inside an intranet, check which registry you are connecting to. You may have been blocked from the npmjs.org registry.

fabiosleal · 2020-10-30T21:55:21Z

$ yarn global add @nrwl/schematics
yarn global v1.7.0
[1/4] Resolving packages...
error An unexpected error occurred: "https://https://registry.yarnpkg.com/@nrwl/schematics: Not found".

More info:
This error happen not only in macOS, but in Linux (Ubuntu, CentOS) too.

In my case, this error was related to some misfunction in docker, probably after some change on iptables rules.

After restart docker service, everything works fine for me.
$ sudo systemctl restart docker

Bruce773 · 2020-11-23T17:04:04Z

run
yarn config set registry https://registry.npmjs.org
will do the job

Worked for me!! 🎉 😁

alihassan143 · 2021-01-16T06:07:23Z

yarn global v1.22.5
[1/4] Resolving packages...
error An unexpected error occurred: "https://registry.npmjs.org/strapi: error:0909006C:PEM routines:get_name:no start line".
info If you think this is a bug, please open a bug report with the information provided in "C:\Users\aliha\AppData\Local\Yarn\Data\global\info Visit https://yarnpkg.com/en/docs/cli/global for documentation about this command.

merceyz · 2021-01-16T12:13:58Z

Closing as there is nothing actionable here, the registry is just a CNAME to npm so need to raise those issues with them
https://yarnpkg.com/getting-started/qa/#why-registryyarnpkgcom-does-facebook-track-us

fast-and-curious-1910 · 2021-01-19T13:00:46Z

I got the same error.

Error:

PS E:\Coding Projects\BLUEIT\blueit> yarn add -D @types/node typescript nodemon ts-node
yarn add v1.22.5
info No lockfile found.
[1/4] Resolving packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
[2/4] Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred: "https://registry.npmjs.org/typescript/-/typescript-4.1.3.tgz: ESOCKETTIMEDOUT".
info If you think this is a bug, please open a bug report with the information provided in "E:\\Coding Projects\\BLUEIT\\blueit\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Node Version: 14.15.2
Yarn Version: 1.22.5
Platform: Windows 10

dadoadk · 2021-03-10T15:01:41Z

This worked for me:
yarn config set strict-ssl false

hitfm00 · 2021-05-13T17:16:48Z

run
yarn config set registry https://registry.npmjs.org
will do the job

work for me!

ghost assigned torifat May 24, 2018

ghost added the triaged label May 24, 2018

kristfal mentioned this issue Jan 10, 2020

Update iOS library + Potential CI fixes rnmapbox/maps#609

Merged

giangdinh mentioned this issue Dec 9, 2020

Creating react-native project with typescript template fails. facebook/react-native#30557

Closed

merceyz closed this as completed Jan 16, 2021

yarnpkg locked as resolved and limited conversation to collaborators May 13, 2021

An unexpected error occurred: "https://registry.yarnpkg.com/<package>: Not found" #5865

An unexpected error occurred: "https://registry.yarnpkg.com/<package>: Not found" #5865

Comments

IlCallo commented May 24, 2018 • edited

bkad commented May 31, 2018

IlCallo commented May 31, 2018 • edited

Jasu commented Jun 4, 2018

chiel commented Jun 6, 2018

sgraham785 commented Jun 6, 2018 • edited

sgraham785 commented Jun 6, 2018

anied commented Jun 12, 2018 • edited

vinujosef commented Jun 13, 2018

Ranhiru commented Jun 20, 2018

peterlavey commented Sep 1, 2018

jamsheedpk commented Oct 16, 2018

jimklo commented May 2, 2019 • edited

jaapaurelio commented May 10, 2019

MartinYounghoonKim commented May 20, 2019

Stoobaart commented Jun 5, 2019

IlCallo commented Jun 10, 2019

Stoobaart commented Jun 10, 2019

vabole commented Aug 15, 2019 • edited

gilmoreorless commented Oct 1, 2019

knoxcard commented Oct 2, 2019 • edited

knoxcard commented Oct 2, 2019

RyanPWalker commented Oct 7, 2019

bobysf12 commented Dec 5, 2019

lirbank commented Dec 20, 2019

coYms commented Dec 30, 2019

doug31415 commented Feb 12, 2020

kaitlynbrown commented Feb 12, 2020

RabeeAbuBaker-Exalt commented Aug 6, 2020

RabeeAbuBaker-Exalt commented Aug 6, 2020

bipindubey-technoark commented Aug 6, 2020

LevanSanadiradze commented Aug 6, 2020

khurram-wasim commented Aug 6, 2020

anthonyminyungi commented Aug 6, 2020 • edited

RabeeAbuBaker-Exalt commented Aug 6, 2020

shinjiber commented Aug 6, 2020

osamaeshtiaq commented Aug 6, 2020

nvtin commented Aug 6, 2020 • edited

kamranblueeast commented Aug 6, 2020

minhhy2801 commented Aug 7, 2020

wadamomo commented Aug 15, 2020 • edited

Pintot commented Aug 16, 2020

Pintot commented Aug 16, 2020

yael-screenovate commented Aug 23, 2020

GitHubAjit commented Sep 6, 2020

andreapiras commented Sep 15, 2020

pak11273 commented Sep 22, 2020

mayooresan commented Sep 28, 2020

fabiosleal commented Oct 30, 2020

Bruce773 commented Nov 23, 2020

alihassan143 commented Jan 16, 2021

merceyz commented Jan 16, 2021 • edited

fast-and-curious-1910 commented Jan 19, 2021

dadoadk commented Mar 10, 2021

hitfm00 commented May 13, 2021

IlCallo commented May 24, 2018 •

edited

IlCallo commented May 31, 2018 •

edited

sgraham785 commented Jun 6, 2018 •

edited

anied commented Jun 12, 2018 •

edited

jimklo commented May 2, 2019 •

edited

vabole commented Aug 15, 2019 •

edited

knoxcard commented Oct 2, 2019 •

edited

anthonyminyungi commented Aug 6, 2020 •

edited

nvtin commented Aug 6, 2020 •

edited

wadamomo commented Aug 15, 2020 •

edited

merceyz commented Jan 16, 2021 •

edited