Hi folks! Just started learning Node here coming from basic web dev background. I am enjoying Node Up and Running by Mike Wilson and Tom Hughes-Croucher (i enjoy oreilly books for their depth) but is it woefully outdated to say the least. What other (relatively up-to-date) books do you recommend we use for learning reference?
Also, I prefer well-written books over videos for their depth. The official docs can be intimidating for begginers. :(
I don't know about book.But definitely, recommand this udemy course https://www.udemy.com/understand-nodejs/. Have Fun!
I can recommend the following books:
Some years ago I read a german book. But it wasn't very good. Later I discovered LeanPub. There are very good books on average.
I didn't read them but there is a "Node Beginner Book" (in English and Português) and a more detailed "Hands-on Node.js" book.
But in general, I would say a good JS book (like "You don't know JS") is worth more than the best Node book. If you played the "learnyounode" course of NodeSchool, you should be ready for Node.
PS: If you want to use JS and C++ (or Rust ;) ) with Node, there is a book too.
Yes.I would like to recommend the following Pro Express.js . The book is largely a review of fundamental express.js knowledge, express modules, with many short examples to illustrate how the modules work, followed by a number of full application based examples that really drive home the knowledge provided earlier in the book. It's a great way from zero to pro quickly. if you want to check more books for advance learner, you can visit here for some best node js books.
Tierney Cyren
Developer Advocate @ NodeSource
I totally get what you mean about books for in-depth information - that's how I learn best as well, and frequently found free videos and courses to be heavily lacking.
That said, it's incredibly hard to find good Node.js books because of how fast Node moves, in comparison with the writing and publishing process of an actual book - which is what it seems you discovered with Node Up and Running.
Here's how I've seen others succeed, and have just started succeeding with myself:
Think of a project you want to build. It doesn't matter what the project does (it could be a command line tool, a simple web app, or a REST API), as long as you decide on something that's simple, something basic. Then, start working on trying to build it.
Figure out what aspects of it need to be built (do you need a CLI assistant to build the command line tool? Do you need web server, like Express, for the web app? What are you going to return from your API - JSON? XML? Images? And so on.) and then look for a tool to do it. Do this for all the aspects of your app - try to limit it to 2-4 aspects (three is probably the sweet spot - 2 will go fast, 4 may be a bit much). Then, start building your app.
Taking this approach will allow you to go as deep or as shallow as you want into the different aspects, without a pre-defined guide that may leave you asking questions. It will also allow you to try different things out, instead of whatever is prescribed by the creator. Finally, it will allow you to learn what's happening at present, instead of what happened 3 months to 3 years ago.
Good luck!