4 ms·

I can see where both sides are coming from, but I think if it's as simple as just uploading a new package with a version bump then the maintainer should just go

I can see where both sides are coming from, but I think if it's as simple as just uploading a new package with a version bump then the maintainer should just go ahead and do it. It's not worth it to interrupt the workflow of everyone else just because you want to "stand your ground" and not spend 5 minutes re-uploading a package.

nathancahill 9y ago
Not only that, but NPM has a process in place now to handle this exact situation: http://blog.npmjs.org/post/141905368000/changes-to-npms-unpublish-policy http://blog.npmjs.org/post/141905368000/changes-to-npms-unpu... The first response (from which the whole thread devolves) claims "npm does not allow re-publishing the same version", which just isn't true anymore.
brepl 9y ago
Not surprised the maintainer gave such short shrift. These commenters should provide a clear fix or demonstration that re-publishing will fix the problem, or just use the previous release. There's also nothing stopping them forking the project and publishing their own 2.8.29-foo as uglify-js-bar and getting on with their lives. Being rude to open source maintainers is very unlikely to make them more helpful.
- marczellm 9y ago
  That doesn't help when you have a transitive dependency.