I'm going through a special version of this hell right now at work. I'm updating old Lambdas that are on the node.js 12 runtime.

Some of them have internal dependencies that just _no longer exist_, or aren't compatible with Node past 14.

Meanwhile, all I had to do to update old Python Lambdas was just update the runtime itself.

Note that in my original comment, I didn't say Python doesn't have version problems. I said my (specifically my) Lambda version migration problems were much worse with Node.js than Python.

Also, I'm vaguely offended that you used a "let me Google that for you" reply as your sole comment. Did you really have nothing more intelligent to add than low-effort snark? Go back to Reddit.

A lot of people have versioning problems in all languages. You said "Meanwhile, all I had to do to update old Python Lambdas was just update the runtime itself. ". You know that isn't always true in Python that you just update the runtime and nothing goes wrong.

The reality is that JavaScript has become an ungovernable language; Python's dependency problems are nowhere near the current horror of JavaScript, where people keep using all these tools made by startups creating problems bigger than the problems such tools were supposed to solve, and those new problems are solved by a wave of new tools from more -or even the same- startups, and this in an endless loop, because people adopt it again.

At work I deal with javascript dependencies, ruby dependencies, php, and others. Dealing with keeping versions up to date sucks in every language I've used.

True, but Node.js is far worse when it comes to dependencies and _their_ dependencies.

It’s only the module resolution bullshit. Typescript is amazing, but module resolution between the browser and node is so terribly fraught it kills the whole experience.