There's no need to jump straight into the deep end of tooling. An iterative approach works really well here - do a brief survey of what tools there are and wha

There's no need to jump straight into the deep end of tooling. An iterative approach works really well here - do a brief survey of what tools there are and what problems they solve. Then, when that problem starts soaking up a lot of time, you can read up on the available tooling in greater detail. There _are_ a vast amount of libraries in the js ecosystem, and it'll take time to fully understand all the different pieces. It took me nearly 2 years to achieve an understanding of most of the buzzwords in that article (and even then, there are some I still haven't worked with directly). In my personal experience, learning JS is very much a BFS process.