Of course it's a PITA to keep up to date because the Node and JS developers live the mantra of "move fast and break things", which is a bad philosophy for commercial development. So project updates are slow and a little at a time, generally to get a new feature or to avoid a CVE that you think affects you.
At my last job, we were at the beginning of a dev cycle which would give us the most testing time, so I started trying to move us forward to a new version of Node, Typescript, and various modules to match. I gave up after about 3 days when I couldn't get things working together, usually because of too much change in the modules which forced structure and API changes. Heck, we even had a module that was on 1.0-rc12 and when it changed to 1.0 the dev did a major API change! Why would anyone do a major API change from an RC to a final 1.0? That's just 1 of the horrors I tried to overcome. Last I heard, they haven't upgraded versions. [This was on a "backend" project, not code in a browser.]
That sort of thing is also why devs will grab 1 function from a module and pull it into their code. Why take the baggage and upgrade burdens of the module and all of the other code for a 10 line function. I wouldn't do that for a module that where security was important, but for some computational work I've done it and don't have a problem with it.
Honestly, the community is its own enemy in that regard and I'm glad to be off that project. My feelings now are that unless you're dealing with frontend browser work, don't ever use Typescript/Javascript.