This is a great question. As you become more experienced in your language of choice, you learn that the best (and only) place to stay "current" is from the source, which in this case is the Node JS website. I know it sucks to hear that, but as you start working with the language more, you actually get to a point where you understand all of the high-level solutions, and only start caring about "edge" cases that are not so common. And anything new and evolving from NodeJS will always be announced on their site (releases, patch/fixes, performance enhancements, deprivations etc...) first. You will also come to appreciate reading the source code more to understand the "why" of it all. I hope this helps, and it is only an opinion of my own. Some devs will most certainly give a better explanation.

I don't think you should always look for dates when looking for resources to learn Node. As you get further down your path, problems become more niche and solutions can still be valid for many reasons. A fun thing to practice could be taking an old tutorial and using the latest version of the packages used, and rewriting a small post on what broke the build and why. This would introduce you to to some errors and get you comfortable with concepts while you search for content. As to finding the best resources, if you are experienced with another language, just dig into the documentation. NodeJS concepts have core concepts and then have great packages that devs pair NodeJS with (expressJS, hapi) that may be a good next step. Start understanding security best practices and "reverse proxy" services (nginx) . Reddit has good groups, start reading news sites like ycombinator and just filter YouTube results for NodeJS to see who gets a lot of views and search their catalog. Don't forget you code node with js, so make sure you join JavaScript communities and understand that path.