How can you move beyond this point?
Expectations: You'll understand JS syntax, types, relationship between objects & functions & closures, scope [issues], inheritance, design patterns, browser quirks, and some maintainable coding styles and good practices.
How to Read This Book: Keep a spiral notebook nearby when reading this book. The first page of this notebook should be a "Definitions" page, where you can write down one-sentence definitions of new syntax and vocabulary terms. You'll want to eventually transfer these terms into Anki and consistently review them (this will make you a fast coder). Read this book away from your computer, and when you want to fiddle with an idea or try something out for yourself, avoid the immediate impulse to grab the keyboard, and instead, mark the page with a post-it (maybe a pink one), and then come back to it when you're finished with offline mode. This general advice applies to all books mentioned in this post.
Key Chapters: It's a big book, but a fast read. Plus, every chapter is not immediately essential. At the bare minimum: read Chapters 1-4, skim chapters 5 & 6 (don't worry about memorizing all inheritance patterns, just understand why OO-style inheritance is tricky, and at least have a good understanding of one of the final 3 inheritance types), read chapter 7, then read chapter 24 (this is a brilliant chapter).
Expectations: You'll become much more familiar testing practices, debugging programs, thinking about code performance (when it's appropriate!), and cross-browser considerations.
Key Chapters: It's a pretty small book and a fast read. The key chapters are 1-6, 12, and 14/15. Chapters 7 and 12 should also be conferred when necessary.
Necessary Background:You should first feel comfortable writing JS applications without a framework. If you're confused by why you should use a framework, you're probably not ready for this step.
Key Chapters It's less than 60 pages. Every example and discussion is important. Read it all =) and build small demo apps to test new concepts. Oh, and if you don't builda TODO list at some point, you're doing it wrong.
Alternatively, several of my colleagues suggested I learn AngularJS, and I'm about 100 pages into the following book (it's great so far, but I can't fully endorse it yet): Pro AngularJS
Expectations: You'll be able to write non-trivial and well-structured node.js servers, as well as interface with the file system and work fluently with data streams.
Key Chapters: Chapters 1-7 will form the core of your Node understanding. You should tackle the remaining chapters as you need them.
Extra: When trying to understand data streams, check out John Resig's excellent http://nodestreams.com/
Feel free to shoot me a tweet at @obphious. Or, if you have any private questions, criticisms, or would like to grab coffee (I'm in Berkeley) feel free to contact me at colorado %-AT-% berkeley %-DOT-% edu. Or, if you'd like to read more of tech/programming/education type posts, you can subscribe to receive very occasional updates.