Yarn install fails for react-router

nodejs
yarn
#1

yarn fails to install react-router although it seems to be available (i can run a clean yarn install locally and if i open the link directly i can download the package).

anybody else experiencing this issue or has a solution?
i’ve tried with “Rebuild w/o cache”

yarn install v1.13.0
[1/4] Resolving packages…
[2/4] Fetching packages…
error An unexpected error occurred: “https://registry.yarnpkg.com/react-router/-/react-router-4.4.0.tgz: Request failed “404 Not Found””.
info If you think this is a bug, please open a bug report with the information provided in “/home/circleci/c2m/yarn-error.log”.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Exited with code 1

#2

looks like a circleci specific issue:

circleci@3ccab2d21a71:~/c2m$ curl -I https://registry.yarnpkg.com/react-router/-/react-router-4.4.0.tgz
HTTP/2 404
date: Thu, 25 Apr 2019 11:30:21 GMT
content-type: application/json
set-cookie: __cfduid=d30947f5142879cfd2f371285d0bd147a1556191821; expires=Fri, 24-Apr-20 11:30:21 GMT; path=/; domain=.registry.yarnpkg.com; HttpOnly
cf-cache-status: MISS
cache-control: max-age=432000
cf-ray: 4ccffc038a3e9a10-EWR
expect-ct: max-age=604800, report-uri=“https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct
vary: Accept-Encoding
server: cloudflare

works fine on my machine:

curl -I https://registry.yarnpkg.com/react-router/-/react-router-4.4.0.tgz
HTTP/2 200
date: Thu, 25 Apr 2019 11:30:34 GMT
content-type: application/octet-stream
content-length: 48720
set-cookie: __cfduid=d22b032cf5ed1b5bdbd1aed8e50a2c11e1556191834; expires=Fri, 24-Apr-20 11:30:34 GMT; path=/; domain=.registry.yarnpkg.com; HttpOnly
cf-cache-status: HIT
cache-control: max-age=432000
cf-ray: 4ccffc581e089129-ZAG
accept-ranges: bytes
etag: “7a2e46507aabcb87174798c57096399b”
expect-ct: max-age=604800, report-uri=“https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct
last-modified: Sat, 16 Mar 2019 01:07:11 GMT
vary: Accept-Encoding
server: cloudflare

#3

A couple observations. The yarn registry is a DNS alias to the NPM registry.

Also, since you are getting a 404, that means the connection from CircleCI to the registry is fine. I do see that your local check is hitting another Cloudflare server (cf-ray:) so it’s possible you are reaching another backend registry server as well (I really hopeNPM has more than one)

I don’t think this is a CircleCI issue, or that we can do anything about it, but I’ll keep an eye out for more reports.

#4

build passed

1 Like
closed #5

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.