Node, npm, node-sass - no, the whole JS universe, you fucking piece of shit!

Fuck you royally!

especially node-sass

JS is bad when you let it be bad; when you don’t let it be bad.. it’s the fucking worst!

Bring eslint to the mix and you’re fucked. At least now I know what happens when you don’t keep on top of the impending dependency hell.

”Hi binari, we need to make changes to this one service frontend which was developed couple of years back and nobody touched since…”

FFFFUUUUUUUU…ck

There goes fucking producivity. Fucking fuck.

When trying to get the bugger even to fucking build, while resolving the fucking dependency hell I ended up in a situation where one dependency requires eslint between v5.something < 7, and other >= 7.5.0 … seriously? You fucking kidding me?

> productivity
> node

pick one.

JavaScript: All the performance of Java, all the security and stability of Flash, all the dumbass bad code of PHP.

so... npm i didn't work huh

@darksideofyay ha… it all started with node-sass dependency in that one lib not being compatible with the node version required to build another lib that… oh well, it becomes a clusterfuck real fast.

Have you looked into Deno?

The same man who created Node started to feel like it became a plugin-mess and needed a bigger set of built-in tooling so he created a new runtime for JS and TS.

(Yes, I understand the initial reaction to this is "WTF, I was complaining about there being too much stuff and now you mention more stuff!" I get it. But I guess you have to create new stuff to move forward")

@jiraTicket last I checked it was not mature enough for prod. Also gave it a spin and wasn’t quite convinced about it. Yes, it addressed some of the issues with Node, but it didn’t really make JS feel less shitty.

Just try to install node gyp ….

Hi so we just need to setup authorization via keycloak on this Angular SPA... Uses Angular 8. Keycloak supports 10+. Current is 12. 85% of our dependency tree is abandoned.. Fml