How are unpublish events handled? about npm-register HOT 9 CLOSED

given npm's policy has changed around this, I'm going to close this. But If there is anything specific you would like to see definitely let me know!

from npm-register.

you won't be able to install them since they won't be included in the manifest, but the tarballs will still be in S3

from npm-register.

well, that's if a version was unpublished, if the entire package disappeared it would still be in elephant

from npm-register.

Continuing in that vein, what happens if the package disappears and then reappears?

from npm-register.

Err, reappears because someone squatted on the name

from npm-register.

if the tarball sha changes it'll be redownloaded

from npm-register.

I don't think generally you can republish the same version again though. It happened once with pad-left, but I think that was a one-time special case.

from npm-register.

you won't be able to install them since they won't be included in the manifest, but the tarballs will still be in S3

Is there a way to ignore this? The whole purpose of elephant is to have a fail safe back up of repos regardless of what happened on npm. Could a setting be added to ignore unpublishing?

from npm-register.

That's not the goal of elephant, the goal is to stay up when npmjs.com is down but npmjs.com is STILL the canonical source of truth. If npmjs.com is up and has a different package metadata it should use that new metadata.

Having said that, an unpublished package would still be available since elephant considers a 404 down.

from npm-register.