Hacker News Reader

NPM hell is what got me to move from beloved TypeScript to Golang. Coming back to pet projects a few months later was true excruciating pain every single time.

Today, it's Go in the backend and Svelte in the frontend, or vanilla JS for very small and simple tools.

View on HN

As someone who programs on backend, frontend, and Android apps, I can't agree more. Javascript frameworks and NPM hell is terrible. You rarely have the problems in Go/Kotlin/Java world that are considered normal in the NPM world.

I never understood this npm hell reference people are speaking off. Is this just the drama of updating an outdated inherited project? I've been working with node/npm since the early days and don't consider it worse than what you find in Java, Python or PHP.

The latest version of webpack removed polyfill, this broke another dependency, and i had to downgrade the react version to fix that!

Nothing like this did I ever see in the go or kotlin world.

If you depend on a specific behaviour why dont you pin your react version?

I learnt that much later. Apparently the current version of webpack that you get by following the official react project setup is missing certain polyfills!

Couldn't you have pinned your dependency and / or installed from a lockfile?

are you leveraging a framework on the backend for Go?

Reply on news.ycombinator.com