Remember the developer who corrupted his libraries which had over 20 million downloads and thousands of dependent projects? In the immediate aftermath, he had complained that NPM had reverted to a previous version of the faker.js package and that Github had suspended his access to all public and private projects. I have 100 projects.
He had his access restored by January 6th, after one of his libraries was forked by the community to create a community-driven project. The developer asked on his account: What's up? You never responded to my support emails after you removed my ability to publish to NPM. I need to maintain 100 packages.
Everyone makes programming mistakes. Nobody is perfect.
It's not known if NPM has blocked his ability to publish, but the initial reaction from other developers on social media suggests that's the case.
All Rights Reserved © 2024
