It's the hot technology in the same way that Rails was the hot technology in 2005-2007.

This does not make it a must-have. I did just fine learning Django instead of Rails in 2007, and when I finally got into Google in 2009, I ended up using neither for the bulk of my time there (okay, I think I had about 3-4 Django projects in my tenure, and knowing Python definitely helped).

There is a certain segment of the employer market that is always chasing the latest hot fad: Java applets in 1997, ColdFusion in 1999, J2EE in 2002, Rails in 2005, Angular in 2009, React or Polymer or Go in 2014. Knowing the latest hot fad can be an excellent way to get your first couple jobs in software, because these employers are always looking for people and typically don't know much about technology themselves. However, it often signs you up for a lifetime of retraining, unless you leverage experience at one of these places into domain knowledge with a longer shelf life. Companies that live by the latest fad die by the latest fad; the same ColdFusion or J2EE skills that got me my first jobs in college are basically worthless now.

Quick search on Indeed shows 56,332 jobs mentioning JavaScript, 4,378 jobs mentioning Angular. So <8%. Plus, the vast majority of those 4,378 jobs are merely including Angular in a list of various frameworks, as examples of technologies they'd like candidates to have experience with — few of them require Angular specifically as a "must have" skill.