Learn enough about each framework to be able to pick and choose technology that suits your current projects, and what kind of projects you envisage you will be working on in the future.
Things do seem to be heading the way of javascript - the direction of browser technology, the expectation for rich web applications etc. I read somewhere a few months ago that javascript is going to be a core language in windows 8 as well, so a good solid knowledge of core javascript is going to be generally useful whether you're working on websites, mobile, or whatever - client side, server side, and desktop apps.
I think that jQuery is a good solid place to start; it's mature, the docs are good, it's got good use of events and callbacks, you'll find your feet with the scoping rules that seem a little odd, and although you have a lot of power available to you, it's not so abstracted that you feel you are relying on magic.
Also, it'll be a good exercise for you to try and build something with a lot of ajax if you haven't before - controlling portions of your page via the dom rather than a full page refresh every time; to really get a feel that you are building a rich javascript web application broken down into client-side modules, rather than being in the mindset of having a back-end application that has a front-end interface with some effects. (I'm saying this because this is where I was not so long ago)
It's when you build something javascript-heavy like that, that you might start to think "I'd like a js framework where I can do MVC" (backbone), or "I'd like a js framework where I can do MVVM" (knockout), and so on. You and your projects flavour what additional frameworks you choose to work with, not the other way round.
node.js could become a major server-side platform down to scalability, I haven't really tried it yet (sorry!) but my feeling is that the biggest things to come out of learning that might be the low(ish)-level network/web tech (if you have been shielded from sending your own headers, listening to ports and so on up until now), and the different approach to concurrency, rather than the language itself.