Skip to content
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

Latest release breaking npm installs on older versions #14

Closed
jamesplease opened this issue Jan 6, 2018 · 16 comments
Closed

Latest release breaking npm installs on older versions #14

jamesplease opened this issue Jan 6, 2018 · 16 comments

Comments

@jamesplease
Copy link

jamesplease commented Jan 6, 2018

Just cross-linking this issue:

cosmiconfig/cosmiconfig#103

I think this is an npm issue, but I'm not sure. Still investigating!


Relevant npm issue: npm/npm#19534

@jamesplease jamesplease changed the title Latest release breaking npm builds Latest release breaking npm installs on older versions Jan 6, 2018
@cormacrelf
Copy link

The code seems to be maintained by @mbensch now, at https://github.com/mbensch/require-from-string

That repo doesn't have issues enabled, so I guess here is the place to be? Except the maintainer won't be subscribed.

@vtyrtov
Copy link

vtyrtov commented Jan 6, 2018

yarn similarly

`yarn add v1.3.2
[1/4] 🔍 Resolving packages...
Couldn't find any versions for "require-from-string" that matches "^1.1.0"
? Please choose a version of "require-from-string" from this list: 2.0.2
error Received malformed response from registry for "timed-out". The registry may be down.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Aborting installation.`

@BlackHole1
Copy link

I have the same problem.

@squigg
Copy link

squigg commented Jan 6, 2018

broken here too - old versions are no longer available and it's breaking builds. I was getting a 404 for a few minutes on the NPM site, seems as though the entire package was taken offline.

mbensch took it over, but now getting the issue below due to missing older versions:

pm ERR! code E404 npm ERR! 404 Not Found: require-from-string@https://registry.npmjs.org/require-from-string/-/require-from-string-1.2.1.tgz

@cormacrelf
Copy link

cormacrelf commented Jan 6, 2018

Yes, the entire website/registry entries for both require-from-string and pinkie-promise (which has had the same version bump) did appear to be completely down for a little while. It was as if each package had never existed, and came back with only one version. I hope this isn't a security issue, but it may be possible that the new maintainer can upload any code they want in the old version slots which were meant to be immutable.

@mbrezovsky
Copy link

angular/cli installation fails due to

sudo npm install -g @angular/cli
npm ERR! code ETARGET
npm ERR! notarget No matching version found for require-from-string@^1.1.0
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'cosmiconfig'
npm ERR! notarget

@jamesplease
Copy link
Author

jamesplease commented Jan 6, 2018

@blackholegalaxy it's not a repository hijack. This is definitely an npm error :)

Turns out I was wrong!

@JAertgeerts
Copy link

https://github.com/npm/registry/issues/255

@mbensch
Copy link

mbensch commented Jan 6, 2018

The original author deleted his account and all his packages. I have re-published a few of them but it's a lot to keep up with right now.

@marco476
Copy link

marco476 commented Jan 6, 2018

Same problem and same npm-issue.
I found this error by create-react-app.

@m4scosta
Copy link

m4scosta commented Jan 6, 2018

With the same problem here, version 1.2.1

@oppodeldoc
Copy link

https://status.npmjs.org/incidents/41zfb8qpvrdj

@m4scosta
Copy link

m4scosta commented Jan 6, 2018

Anyone knows which versions are available?

@jamesplease
Copy link
Author

@Marcospy 2.0.2, but all of the versions should be back up once npm fixes their problem. Also, 2.0.2 may be removed at that time given that someone else published over the missing package.

@rhinonan
Copy link

rhinonan commented Jan 7, 2018

I have the same problem......

@jamesplease
Copy link
Author

Should be fixed now @rhinonan (see https://status.npmjs.org/incidents/41zfb8qpvrdj ). Closin'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests