Skip to content
This repository has been archived by the owner on Aug 23, 2018. It is now read-only.

Many packages suddenly disappeared #255

Closed
antoniobrandao opened this issue Jan 6, 2018 · 1,263 comments
Closed

Many packages suddenly disappeared #255

antoniobrandao opened this issue Jan 6, 2018 · 1,263 comments

Comments

@antoniobrandao
Copy link

https://www.npmjs.com/package/infinity-agent
https://www.npmjs.com/package/timed-out
https://www.npmjs.com/package/pinkie-promise

All dependencies of webpack-related modules

@JAertgeerts
Copy link

https://www.npmjs.com/package/require-from-string

@girishla
Copy link

girishla commented Jan 6, 2018

massive issue for us because of this. Please resolve asap

@girishla
Copy link

girishla commented Jan 6, 2018

I've tweeted npm support and also emailed them. Hope someone sees this soon

@allquantor
Copy link

npm/npm#19534

@jamesplease
Copy link

jamesplease commented Jan 6, 2018

I believe this issue affects packages with versions before 2018 as well as versions after 2018.

Versions before 2018 cannot be installed, while versions after 2018 can be. For instance,

[email protected] is unavailable, while [email protected] is available. The difference between them is their publish year. Note that 2.0.2 was just published, which kicked off this series of problems.


Update: This theory appears to be wrong. See @BlackHole1 's comment below :)

Instead, this appears to be because floatdrop's packages have disappeared.

@BlackHole1
Copy link

@jmeas Not so, because someone registered the package

@antoniobrandao
Copy link
Author

They come and go.

Just today I've seen the package "infinity-agent" missing, then it came back, disappeared again, and came back again.

Very flimsy behaviour from NPM.

@jamesplease
Copy link

jamesplease commented Jan 6, 2018

Ah, I see @BlackHole1 . That makes sense.

If that's the case, then this is a big security issue if someone hijacks a critical project and replaces it with some malicious code.

@teawithfruit
Copy link

@jmeas And I thought that this was only a "problem" between 1999 and 2000. ;)

@robbiethegeek
Copy link

@jmeas https://www.npmjs.com/package/require-from-string doesn't exist at the moment is that the page for your module?

@antoniobrandao
Copy link
Author

I just HOPE during this time it is not possible to actually create a new package with the same name as these missing ones. So many projects would have their dependencies broken.

@girishla
Copy link

girishla commented Jan 6, 2018

there should be a mirror for isssues like this

@mbensch
Copy link

mbensch commented Jan 6, 2018

@antoniobrandao It is possible. I have re-published some of the packages that were missing with the code that was available on git-hub. The original author has deleted his NPM account and dropped all his packages. But it seems like NPM keeps dropping packages. No idea why.

@antoniobrandao
Copy link
Author

@mbensch OMG 😨😨😨😨

@lafama
Copy link

lafama commented Jan 6, 2018

This one package https://www.npmjs.com/package/duplexer3 was unavailable for close to 30 mins. Now it back but interesting thing is that it appears its was published 5 mins ago

jekh published 19 minutes ago

@antoniobrandao
Copy link
Author

So much for NPM reliability.

@paulwib
Copy link

paulwib commented Jan 6, 2018

Looks to me all these packages were originally published by @floatdrop, see google cache. Anyone seen any other users affected?

@mbensch looks like his account still exists just all packages gone.

@marco476
Copy link

marco476 commented Jan 6, 2018

Same problem for require-from-string package that don't allow me to use create-react-app.

@ghost
Copy link

ghost commented Jan 6, 2018

@marco476 same here, can't even install create-react-app

@kiichi
Copy link

kiichi commented Jan 6, 2018

thanks, it's working now.

@Jakob-em
Copy link

Jakob-em commented Jan 6, 2018

Yeah up and running again

@devdigital
Copy link

pinkie-promise delivered here, pain now subsiding

@shacal
Copy link

shacal commented Jan 6, 2018

Sysadmins replacing Intel machines with Raspberry PI's :D

@WojciechBanas
Copy link

You nearly caused nuclear war.

@uneco
Copy link

uneco commented Jan 6, 2018

2018-01-07 6 45 36

Good night you guys

@fathyb
Copy link

fathyb commented Jan 6, 2018

let me be the last oneeeeee

@WojciechBanas
Copy link

You nearly caused nuclear war.

@Repflez
Copy link

Repflez commented Jan 6, 2018

we ded jim

@julkue
Copy link

julkue commented Jan 6, 2018

wooorks! whooop whooop.

1 similar comment
@julkue
Copy link

julkue commented Jan 6, 2018

wooorks! whooop whooop.

@retep998
Copy link

retep998 commented Jan 6, 2018

And this is why you should never use Javascript.

@julkue
Copy link

julkue commented Jan 6, 2018

wooorks! whooop whooop.

@shacal
Copy link

shacal commented Jan 6, 2018

Sysadmins replacing Intel machines with Raspberry PI's :D

@bnymncoskuner
Copy link

I have a nice story to tell my grandkids one day. It's been fun guys!

@anirudhmurali
Copy link

Get together is done. Get back to work y'all!

@Repflez
Copy link

Repflez commented Jan 6, 2018

morale of the story: cache everything?

@julkue
Copy link

julkue commented Jan 6, 2018

wooorks! whooop whooop.

@tariqinaam
Copy link

backend dev somehow got part of this..

@lazarljubenovic
Copy link

GitHub so overloaded you can't even lock the issue? 😂

@Fabricio20
Copy link

Why aren't there copies of the npm repository like maven so there isn't a single point of failure?

@uneco
Copy link

uneco commented Jan 6, 2018

what was I gonna do...?

@Adohk
Copy link

Adohk commented Jan 6, 2018

first

@shacal
Copy link

shacal commented Jan 6, 2018

Sysadmins replacing Intel machines with Raspberry PI's :D

@artemkovalev92
Copy link

Party's over 🎉 Happy Saturday night coding

@danielweck
Copy link

pinkie 2.0.5 has just been published by some other dev! (not original https://www.npmjs.com/~floatdrop )
https://www.npmjs.com/package/pinkie
https://www.npmjs.com/~puradox
@floatdrop

@shacal
Copy link

shacal commented Jan 6, 2018

Sysadmins replacing Intel machines with Raspberry PI's :D

@npm npm locked as resolved and limited conversation to collaborators Jan 6, 2018
jakesylvestre referenced this issue in MrMEEE/bumblebee-Old-and-abbandoned Oct 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests