New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency Broken (2-thenable) - 404 #7321
Comments
@lfreneda it looks as some npm registry issue on your side.
|
@mjbrowning1 we are having this issue on GitHub Actions and Codeship :( |
There's probably some npm registry caching/mirroring issue in AWS CodeBuild |
@medikoo Not sure :( |
We were having this issue when fetching 2-thenable with npm 5.3.0. After upgrading to npm 6.13.7 we are no longer having this issue.
|
We are also having the same issue with CodeBuild. We would appreciate any help! 1 | [Container] 2020/02/11 22:37:38 Waiting for agent ping |
Having the same issue but not in CodeBuild. This is in AWS however. yarn install v1.21.1 |
Please report to AWS support, that there's some issue with npm registry mirror on their side. |
I'm seeing this from 2 different machines, my local MacBook and a linux box at home:
Not really a |
Just tried to install npm on mongoDb boilerplate and got error message// |
Same problem here, local machine, using yarn 1.22... |
Just got this problem on a alpine linux running a CI pipeline @ gitlab, using |
I've send also support ticket to npm (maybe it's related to some updates to registry on their side, which started to propagate now) |
Copied and pasted your comment and submitted to AWS support. |
Newer npm versions are working fine. |
changing the registry on yarn with
didn't fix it either. |
ran |
Capturing the request from |
I started to observe this locally. It's evident npm registry issue. When registry query is issued with Following returns curl -i https://registry.npmjs.org/2-thenable Following curl -i -H "accept: application/vnd.npm.install-v1+json" https://registry.npmjs.org/2-thenable I have opened an npm support issue for that (but still there's no answer). It may help if you open other request on npm support to increase awareness of a problem |
We're having this issue with AWS Codebuild. But it sounds to me like others are having it outside of AWS, correct? |
Yes, it's npm registry issue. See: #7321 (comment) |
Cheers @motts1 solution worked for me, was able to install on Node 8.10 after updating npm |
I just upgraded our AWS codebuild from the standard 1.0 image to standard 3.0 and the problem went away. I figured that might have a newer version of npm. Edit: I also had to upgrade our C# lambda build project from windows-base:1.0 to windows-base:2.0. Edit edit: well now that broke our C# lambdas, I guess I'll wait for the npm fix |
Response from npm:
|
same for me |
problem fixed by updating codebuild env to use aws/codebuild/standard:3.0 |
I am experiencing this issue on a Bitbucket pipeline build. UPDATE: upgrading the pipeline image to
|
I am not sure if this will apply to anyone, but our issue was node version.
|
Grabbing directly from Github works in CodeBuild:
Also, updating npm fixed it in CodeBuild standard / nodejs:8 runtime
|
Thanks Shariq :) |
Still getting this 7 hours on from the comment, how long might it take to propogate? |
Do use local npm of node js like |
i update npm to latest to solve |
I had issues on build containers and locally on macOS. I found changing the yarn registry worked:
Edit: I also use nodejs 10.x because packages like the serverless-image-handler don't support 12.x yet |
Still an issue for us. Nodejs 10.x Edit: fixed for us! |
Working here, thanks! |
Hi all - I work at @npm and we're very sorry about the We have identified the issue on our end and rolled out the fix. Unfortunately, its going take some time to propagate through all our nodes in our CDN layer. You can follow along for progress via the incident on our status page Also, you if you have other packages affected then please feel free to contact our support team directly. |
Thanks @nomadtechie , Must be a bit of a headache there at @npm for you |
@nomadtechie thanks a lot for the update. It's still happening for this package using yarn. |
This worked for me. But can someone explain why this works? |
The funny part is that when I change the ; ~/.npmrc
registry=https://yarn.npmjs.org
|
Interesting - it seems to happen to packages that start with a number. |
@arafatheds Are you using a package registry other than NPM (e.g. Github)? If yes, then the the following might help (it's fixed the issue for me):
|
I think the issue has been solved. I no longer need to have Thanks. |
It seems to be working now on AWS Codebuild. |
It works for me now. Anyone still gets 404 error for following? curl -i -H "accept: application/vnd.npm.install-v1+json" https://registry.npmjs.org/2-thenable |
This error is fixed for us. |
Its works for me without doing any changes.. Thanks everyone for your support |
seems like Thanks everyone 👯♀️ |
❗️ NOTE FROM MAINTAINERS ❗️
It's an issue on npm registry side, where for requests which include the
accept: application/vnd.npm.install-v1+json
header a404
response is returnedFollowing returns 200
Following 404
curl -i -H "accept: application/vnd.npm.install-v1+json" https://registry.npmjs.org/2-thenable
I was informed that issue is already fixed on npm side. Still it may might take a couple of hours to propagate across all nodes and CDN layer.
Hello there!
I'm getting 404 err when installing serverless with:
npm install serverless
, check this out:Is someone facing the same problem?
The text was updated successfully, but these errors were encountered: