Except for arithmetic operations JavaScript has has reached execution performance parity with Java which therefore renders Java functionally obsolete, so there’s that.
By far the greatest limitations I have encountered with JavaScript (after doing everything right) is garbage collection on ultra high frequency operations and opinionated stupidity in the browser space. Don’t worry about the garbage collection until it becomes a provable problem for your application because by then you should have the resources to solve for those business concerns with binaries written in Rust, Zig, C, or whatever.
The browser stupidity impacts hiring maturity. Working in the browser, when done right, is no different than working in the file system because the backbone of everything is a big tree model, but most people are distracted by pretty colors and cannot see the forest for the trees.
I’ve used Node before but I’m sure you’ll have some number crunching and background jobs and what not. You could use Go to build all these things out and go far before you use some specific technology for it. You don’t need to install half the internet worth of dependencies to do basic things.