FWIW, that specific problem with NPM’s package distribution system was indeed fixed…
Andrew Meyer
182

Doesn’t change the fact that it should never have happened in the first place.

People raised it with the NPM devs numerous times in the past, and were always told to stick it. Suddenly one of the root packages is gone, and they’re going back on their word faster than a crack whore half-way through rehab.

npm is NOT a mature environment. There’s only one JS framework that I can think of right now that is even REMOTELY mature, and for some reason everyone is trying to move away from it — jQuery.

How many other libraries/frameworks/etc have bothered with a proper upgrade path, and side-by-side installs.

Like what you read? Give Peter Dolkens a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.