A small Library crashes in the JavaScript Ecosystem into Chaos

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.

An Update on a tiny JS library has plunged on Saturday, a large part of the JavaScript Ecosystem into Chaos, several million projects were affected. The irony of the story: the Chaos was caused by a two-line JavaScript Library. The whole Situation is reminiscent of the infamous Leftpad-Case in 2016, as the Unpublishen of the Packages caused far-reaching problems. The new Bad guy is a two-liner called the is-promise, a Package that can be checked in Production, whether a JS object called a promise. Back to the developers to get depending on your case true or 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.

Faulty Update

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

Similar to 2016, with Leftpad for the first time, a tiny Library Ecosystem caused similar Chaos in JavaScript, to stir up this incident, the discussion on the modularization of Code inside the JS Ecosystem. One side is of the opinion that the modularization is driven in the case of so-tiny Libraries that are used for such trivial tasks, easy-to-far. Code that you’ve written, at least, be under its own control:

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.

Fits to:

This could also interest you

Ready to see us in action:

More To Explore

Enable registration in settings - general
Have any project in mind?

Contact us: