Thanks man, much appreciated

Hey Santiago, I appreciate the read! Wow, that would be a huge change. I would even consider switching to FNM if they can stabilize the feature. In my opinion, it is the best way to manage the Node version.

I appreciate the input, Bernardo! Is it still a problem with modern-day IDEs?

Thanks for the read Tushar! There are just too many version managers to mention all of them in one article. That’s why I picked just five. Maybe I'll post one or two more articles to review more of them. But I bet that they won't cover all of the managers either.

Hey David, thank you for reading the article. I appreciate it! You're right. We can use the .nvmrc file to declare the Node version for specific projects. And I'm mentioning it in the article. You're also right that we can configure shell run run nvm use on cd . However, the reason why I decided not to include it in the article is that it is not maintained by the NVM team. To me, it looks more like a community attempt to fix the initial problem in the same way as nvm-widows doing it. That's right, N does work with Fish as all of the other managers in this list except NVM by default. Do you use it with .nvmrc ? For me, the best part about N is the ability to detect the Node versions just based on the engines section of the package.json file.

Hey Christopher, thanks for the read, and I appreciate your input! I should've added the note of using .npmrc ; that's a miss for sure. As for "doesn't require any separate configuration." We pretty much do have a separate configuration in the .npmrc file. In my ideal world, every tool that claims to manage the Node.js version should take it right from the engines section of package.json , like N does it. Volta is pretty close to the ideal since it places configuration right inside of the file, which makes it easier to keep those sections in sync.

Thanks for the read! Good catch, I'll update the text :)

Appreciate it