I think you should look at the chaotic mess of JavaScript, not as a mental challenge but an opportunity.
I did the typical career path for developers. From Dev to Project Management to Enterprise Architecture and actual management and I hated it. So I found myself a development job again, and this happened to be one that uses a lot of JavaScript. It’s been great so far, because JavaScript isn’t actually that bad when you do it right.
Which is where the opportunity lies. Because it’s sooooo easy to do things wrong. Need to connect to a named instance or a msSQL server in azure? Tedious is going to be your first result, but tedious sucks. Then maybe Sequelize? Can’t connect? Yeah, you, me, and everybody else in a range of closed GitHub issue. Enter node-mssql which works, but in such a horrible way that you’re either a magician or building technical depth the moment you install it.
Except Sequelize runs on Tedious, so why isn’t it working? Aaaah, the documentation is just really poor for connecting to named instances on a msSQL server in an enterprise network. But once you figure it out, you have an ORM that’s basically as good as Entity Framework.
See what I’m getting at here? 15 years ago I would’ve gone with the mssql step and never thought twice about it. That was before I experienced a decade of cleaning up my own hurried mistakes. I’m not going to claim I’m a good developer or this is some sort or revelation, it’s exactly the opposite intact. But since most of us are mediocre, there is plenty of work for those who are old and mediocre. ;)