You sound really motivated and I don't want to put you down or take that away from you. But - I think you have a long way to go before you can say you've "mastered" one or the other, let alone have a good foundation of Javascript. Even if you spent 14 hours a day for 2 months working in javascript, your still short years of experience that most employers look for.
What have you accomplished in these 2 months? Did you put code into production? Did people use that code? Did you fix bugs they found? Did you test the code?
Get good at 1 thing. I mean really good. Good enough that someone could walk up to you - ask you how to create a function in JS or how to delete a DOM element or how to do a for loop or how to loop through a list of objects in an array. Without using a framework.
Then - pick a framework and stick with that. You can find jobs for AngularJS 1.x just as easily as you can find jobs for React. AJS 1.x isn't going anywhere. It has a huge user base; has been around for years; bugs worked out, etc... AJS 2.x is only going to change ALL of that, introduce new bugs and start with a fresh user base.
If you intend to be a career programmer, you will never stop learning. There isn't 1 framework to learn thats the best. Today, AJS 1.x and React are popular - tomorrow - they won't be and something else will be new and exciting.
Every programmer I've meet that learned programming because they needed a job or were looking to make quick money or ... has failed. This can be an incredibly difficult and infuriating job - as well as incredibly rewarding. To say you "learned" javascript in 2 months is almost insulting. I learned AngularJS 1.x in 2 months also. I've worked with it for 2 years now and still don't know everything about it. I spent 7 hours 1 day last week trying to do something in AJS 1.x - finally figured it out, and then removed the code (saved it, of course) because when I took a step back and looked at it, I went down a path that could be achieved much easier a different way.
All of that said -
Keep going. Get on a server and write apps. Doesn't matter what they are; write some code, put it in production; show people it - get feedback - fix stuff - rinse and repeat. Post the projects here and let people critique them. Doesn't matter what it is; reproduce Twitter; reproduce Hashnode; reproduce Amazon. What ever interests you.
Then, after you have some projects to show; put them on your resume and go shopping for a job.