Remember Leftpad in the year 2016? As a developer just decided to unpublishen the Package and millions of other projects plunged into economic Chaos? Something Similar happened over the weekend.
false. Although is-promise consists of only two lines of Code and only a Boolean returns, the Library is one of the most used npm packages at all. is-promise is found in 3.4 million projects and is used in 766 the other JS Libraries as a Dependency.
At the weekend, the is-Promise Library received an Update you should outsourcing work in the Module Standard. This is apparently something went wrong: After the publication of the update crashed the projects, the use of is-Promise in your Build Chain. The IT module Support had been implemented in the Update of the Library, apparently in error. With immediate effect: Both smaller, private projects, as well as some of the largest projects within the JS Ecosystem, including Angular, nuxt.js affected
create-react-appAVA or Google’s Firebase-Tools.
Compile new versions of the impossible
Fortunately, the Bug crashed no existing projects, so there was no factual Downtime. But he disabled the compilation of new versions. Hours later, the Team, the Library is not rolled out an Update in which they managed to fix the problems. Finally, you decided that IT is-modules-Support for the time being, to withdraw.
Face To Stir Up Debate
The argued against side, it is that modularization is super valuable, because it allows to solve a task using a module in an efficient way, instead of forcing every developer and every engineer your own solution for your particular projects.