-
Notifications
You must be signed in to change notification settings - Fork 47
Many packages suddenly disappeared #255
Comments
massive issue for us because of this. Please resolve asap |
I've tweeted npm support and also emailed them. Hope someone sees this soon |
Update: This theory appears to be wrong. See @BlackHole1 's comment below :) Instead, this appears to be because floatdrop's packages have disappeared. |
@jmeas Not so, because someone registered the package |
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. |
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. |
@jmeas And I thought that this was only a "problem" between 1999 and 2000. ;) |
@jmeas https://www.npmjs.com/package/require-from-string doesn't exist at the moment is that the page for your module? |
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. |
there should be a mirror for isssues like this |
@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. |
@mbensch OMG 😨😨😨😨 |
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
|
So much for NPM reliability. |
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. |
Same problem for |
@marco476 same here, can't even install |
thanks, it's working now. |
Yeah up and running again |
pinkie-promise delivered here, pain now subsiding |
Sysadmins replacing Intel machines with Raspberry PI's :D |
You nearly caused nuclear war. |
let me be the last oneeeeee |
You nearly caused nuclear war. |
we ded jim |
wooorks! whooop whooop. |
1 similar comment
wooorks! whooop whooop. |
And this is why you should never use Javascript. |
wooorks! whooop whooop. |
Sysadmins replacing Intel machines with Raspberry PI's :D |
I have a nice story to tell my grandkids one day. It's been fun guys! |
Get together is done. Get back to work y'all! |
morale of the story: cache everything? |
wooorks! whooop whooop. |
backend dev somehow got part of this.. |
GitHub so overloaded you can't even lock the issue? 😂 |
Why aren't there copies of the npm repository like maven so there isn't a single point of failure? |
what was I gonna do...? |
first |
Sysadmins replacing Intel machines with Raspberry PI's :D |
Party's over 🎉 Happy Saturday night coding |
|
Sysadmins replacing Intel machines with Raspberry PI's :D |
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
The text was updated successfully, but these errors were encountered: