When I search for problems with npm libraries and StackOverflow's answer is

"just downgrade the package to {VERSION} and it should work"

It makes me wanna die. How in the clusterfuck is that an acceptable solution?

the modules thing fucked everything up and then I left

- "waaaah I only want the library once but the version isn't compatible"
- "waaaah why does it have to install X different versions, so much bloat"
Choose one

This applies to package management everywhere, not only npm

@devRancid true, but node has the microframework architecture going one resulting projects to have MANY dependencies. I don't understand these programmers at all. Unreliable software, that's the price for being lazy. Software is regarding dependencies just as life. You should not have them without absolutely needing it. And those people, do. Take C applications, working for decades. Dependencies? Niente. Outdated? Nope. We should learn smth from that. If people need some dependency, try to understand it and implement it yourself. So many people are convinced that a dedicated project written by someone else is so much better. Sad if that's your attitude. People who keep installing othermans stuff without investigating how it works will never increment their level. Ok, there's some personal frustration here. A friend told me recently that you should never write a http server yourself because it would be insecure. That's just offensive, ofcourse you can do this. Easy

While ago i did tried everything using NPM to communicate with a shared object file. Forgot the name of that lib. Every version of node tried. Even went completely down to 8. Every version of that package tried - nothing. Under python, it works directly out of the box. And Deno, Deno worked directly as well, so I was very fond of Deno. But Deno marked it as very experimental. How can communicating with a C library be so experimental. Like if that thing is doing smth else..

Wrote a beautiful SQL orm recently. It's in full development. I make querying data using sqlite in C EXACTLY as easy as with python. Just one line required to update / insert a record with prepared statements in the background. Normally, it's a shitload of C code to execute a prepared statement query with C. It's made to be a nice API, not for performance: https://retoor.molodetz.nl/retoor/...

Altough, the performance is quite surprising. Don't know how it's possible. It's really inefficient.

In my experience those dep problems r usually the fault of a big ol’ cluster package who a) doesn’t have their shit together or b) hasn’t been maintained in forever