How one developer just broke Node, Babel and thousands of projects
theregister.co.uk
How one developer just broke Node, Babel and thousands of projects
1–10 of 15 posts
Re: How one developer just broke Node, Babel and thousands of projects
#2It seems like it was less the developer than the package system.
Re: How one developer just broke Node, Babel and thousands of projects
#3I completely agree with the developer here, I also think npm crossed the line by republishing the module.
Re: How one developer just broke Node, Babel and thousands of projects
#4It seems like it was less the developer than the package system.
"When NPM took Kik away from the developer, he [...] unpublished all of his NPM-managed modules"
Re: How one developer just broke Node, Babel and thousands of projects
#5This is gold...
A module for padding the left of a string?!
Used by big projects like Babel?!
NPM takes down a modules without asking the dev
NPM republishes another module without asking the dev.
Then the whole NPM3 mess (unrelated to this article)
If have the feeling those people there have no clue whats on.
Re: How one developer just broke Node, Babel and thousands of projects
#6Re: How one developer just broke Node, Babel and thousands of projects
#7Earlier quoted context omitted.
"When NPM took Kik away from the developer, he [...] unpublished all of his NPM-managed modules"
Which was his right as the publisher of the modules. Open Source Public Domain.
Which should make anybody depending on such "publishers" think carefully about the effects of such dependencies.
Re: How one developer just broke Node, Babel and thousands of projects
#8I completely agree with the developer here, I also think npm crossed the line by republishing the module.
Yeah, though I'm curious what the proper solution would have been.
It seems to me that once published to NPM there should be some process for deprecating a module that is then "unpublished"... rather than just breaking every module that uses it as a dependency instantly.
They could spawn automatic emails to all dependent module owners about the hard deprecation and give them 7-30 days to replace the module before it's removed from the package ecosystem.
Re: How one developer just broke Node, Babel and thousands of projects
#9There was a heated debate last week when someone choose to distribute a 100 lines css framework via npm... I've chosen my side.
Re: How one developer just broke Node, Babel and thousands of projects
#10This is gold... A module for padding the left of a string?! Used by big projects like Babel?! NPM takes down a modules without asking the dev NPM republishes another module without asking the dev. Then the whole NPM3 mess (unrelated to this article) If have the feeling those people there have no clue whats on.
it's not one module at question here. it's 250 modules with thousands of installs.