Oh I keep the hell away from all things javascript as much as possible, I've only had to work with node in a couple of projects, mostly did bugfixes to other people's old code and migrated some APIs away from node to Kotlin as that was the company's main tech stack and we didn't have a single backend engineer who wanted to do Node, those APIs were built by someone who'd long left.

These days if I create a new API for a personal project, it's going to be in Rust and for professional projects it depends on what I'm being paid to use. And for personal projects, since Rust is so heavily focused on the one single build environment that is Cargo, I don't really see the need for docker - usually the pain points are people not having postgres or openssl installed on their machines, but you can just stuff it in the readme that it's necessary, and you get build time errors rather than runtime errors if they're not present. I always prefer build time errors myself.

For work I still use docker, but my main client has a fairly robust setup, where I don't really need to worry about much, but when there is an issue, I'm usually the person who fixes it because the CTO is busy and most internal employees' time has been scheduled already, whereas I get the "oh we need this today, can you do it?" stuff