[j1elo]

I guess we could have a documentary series!

Next up, npm link: broken by design

Synopsis of the chapter: A command with broken behavior that has been reported since as early as 2015, but that "got lost" every time the winds changed and the project decided to change where to manage bugs. What will happen in the latest attempt from an affected user? Tune in and be ready for an exciting ride!

https://github.com/npm/cli/issues/2372

Spoiler: bugs are not sentient beings that solve themselves just by closing the issue (or the whole issue tracker, for that matter).

EDIT to clarify: Sorry for the snarkyness. I just find it funny in a sarcastic way that up until I reported the issue in 2020, the issue had been reported repeatedly but "lost" in the way because the project closed or ignored the issue every time it changed issue tracker. Which happened twice since 2017! so go figure the amount of reports that had gone to waste. On the flip side, this time they haven't changed platforms (yet), although the issue has been closed prematurely anyway.

[hinkley]

npm has been buggy for so long that it is actively driving me away from NodeJS.

I would like to wait to see if the rearchitecture for npm 7 actually allows them to test for regressions more productively, but at this point I don't know if I have the stamina to wait for my company to migrate to node 16.

Someone offers me a job doing Elixir or non-webapp stuff and I'm out. Probably permanently.

[earthboundkid]

Node is the new IE.

[mikewhy]

Funny, because Yarn does do what you expect here and I absolutely loathe it.

[winrid]

What's to loathe about Yarn? I only used it briefly buy in comparison to NPM there were less surprises.

[lioeters]

It reminds me, that exact issue is why I switched from `npm` to `yarn` a few years ago. Sad to see that it has not been solved after all this time..