I would suggest finding a framework you like and can pickup quickly. I had started with Angular 1, liked it, then there was the big change in Angular 2. Hated that. But it did send me on a quest through frameworks, and Aurelia was the one I liked, understood, and didn’t mind spending time on.
As far as how that relates to employment, I create custom widgets using Aurelia for one of my companies primary applications. Luckily, at most customers, I can choose the framework and technology (JSP vs JS Native vs PHP vs JS w/Framework). The reality though is, while my strong suit at this time is JS (nee Typescript) with Aurelia, I have to also be able to work with all the other technologies, and for some customers I have to use the tech that their developers use.
So I’d say choose one framework because you like and are interested in it, then choose another that aligns with your employment. If it’s the same framework, all the better. After that, at least look into what all these other things are and evaluate them. Some might be more appropriate for certain jobs than others. Think of it like the average car mechanic. They learn and train on one kind of car, then when the new model, or different make comes in, they pick up a book, learn it, then fix it.