Intentional Removal from NPM?

[jangerhofer]

I noticed that this package has been removed from the NPM registry while installing a project which depends on timed-out. As far as I can tell, the removal was recent -- from the last two days or so.

Please disregard my issue ticket if the change was intentional; I merely want to make sure you, @floatdrop, are aware!

[antoniobrandao]

Same problem here. Trying to install

nodemon-webpack-plugin

fails because timed-out is missing.

But NPM modules are supposedly impossible to remove by users at this point so this might be a problem with NPM. Also other NPM modules are not showing up, and later showing up again.

Probably a NPM registry problem.

[antoniobrandao]

They say the status is OK

https://status.npmjs.org/

[jangerhofer]

NPM modules are supposedly impossible to remove by users at this point

I did not know that, but that policy certainly makes sense! Perhaps it is simply a temporary outage.

[antoniobrandao]

https://docs.npmjs.com/cli/unpublish

Quote:

With the default registry (registry.npmjs.org), unpublish is only allowed with versions published in the last 24 hours. If you are trying to unpublish a version published longer ago than that, contact [email protected].

I've been having this problem installing other webpack-related modules, and some of them have been restored in the meanwhile. Eagerly awaiting for timed-out to come back too.

[teawithfruit]

It's not only the timed-out package. https://www.npmjs.com/package/pinkie is another package of @floatdrop and it's gone too. I hope that this is a temporarily npm registry error.

[JAertgeerts]

I have the same issue with require-from-string, most likely npm

[antoniobrandao]

Opened an issue in the NPM registry

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

[girishla]

yep, same problem

[jangerhofer]

I had the same error from ‘require-from-string’ about half an hour ago, but it resolved itself before I posted this issue. Seems like it should work itself out indeed.

…

On Jan 6, 2018, 14:23 -0500, Girish Lakshmanan ***@***.***>, wrote: yep, same problem — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[antoniobrandao]

@jangerhofer yeah some packages seem to come back, some others not.

Just today I've seen the package "infinity-agent" come back, disappear again, and come back again.

Very flimsy behaviour from NPM.

[teawithfruit]

https://twitter.com/npmstatus/status/949728719450460161 ."require-from-string" is also a @floatdrop package.

[jasonbarry]

All of @floatdrop's packages are missing... https://www.npmjs.com/~floatdrop

[tommymcdonald]

Creating a new create-react-native-app package fails on this as well, this is a very large project dependency.

[mhingston]

Related: Many packages suddenly disappeared #255

[antoniobrandao]

Beware before visiting https://github.com/npm/registry/issues/255

You can't unsee.