3 ms·
npm’s policy makes sense. But couldn’t it be circumvented by “updating” your package to an empty file or nonsense code?
by ano-ther 3y ago
npm’s policy makes sense. But couldn’t it be circumvented by “updating” your package to an empty file or nonsense code?
- baobun 3y agoNo. If foo@1.2.3 is already published, you can not overwrite foo@1.2.3 - you'd publish foo@any.other.version (typically something at least ^1.2.4) and mark foo@1.2.3 as deprecated (which won't actually make it unavailable like an unpublish would).