3 ms·
leftpad was a social issue. It's been solved by policy on the registry side stopping packages depended on by many others being unpublished.
by nailer 10y ago
leftpad was a social issue. It's been solved by policy on the registry side stopping packages depended on by many others being unpublished.
- ag_dubs 10y agoactualyl at this point, unless there is a legal request or a serious security issue, we don't allow any unpublishes. we encourage transferring the package to the npm user and deprecating it. yay immutable registry!
- steveklabnik 10y agoIt is unclear why this is downvoted: this is an npm employee who made the requisite policy changes after left pad happened. http://blog.npmjs.org/post/141905368000/changes-to-npms-unpublish-policy http://blog.npmjs.org/post/141905368000/changes-to-npms-unpu...
- pluma 10y agoIf by "social" you mean bad decisions on settling a naming dispute, yes it was a social issue. That issue hasn't really been addressed publicly (the official policy still doesn't specify how disputes are decided by npm when no amicable agreement can be reached -- other than what essentially boils down to "we'll do what we feel is right"). The actual disruption however was solved by npm Inc disabling unpublishing (except for some very specific circumstances) and by creating a dummy account unpublished modules are reassigned to to avoid abuse (whereas previously anyone could simply claim unpublished modules and publish new versions).
- nailer 10y ago> If by "social" you mean bad decisions on settling a naming dispute, yes it was a social issue. No, I mean someone retroactively removing a package others were using out of spite.