I think the trick is to move from "must know all" to "what is the problem at hand". What is your current pain? That is where your research and read efforts should go I think, for the rest it should suffice to do some headline scanning.
For example: I originally started out with browserify because I found it simpler to setup then webpack. After a while I run into some limits of browserify and researched whether webpack could address those (only started really reading about it at that point, before it I just knew the name). Now there is quite some buzz about rollup. It might be better, feature wise or conceptually. Yet I don't invest time in it at this point because I don't have any urgent pains with webpack and I'm comfortable with it. If I would start on a green field, long term project, I would probably invest time in reading about rollup because it might be a better investment in the long term.
TL;DR: pick your battles, focus on your current pains. Nobody expects you to know everything.
(... and if you are desperate to learn new things, try MobX ;-))