I’ve heavily promoted nvm, a Node.js version manager, over the years. Having a tool to manage multiple versions of a language interpreter has been so useful, especially due to the complexity of Node.js package management.
One tip I like to give new developers is adding a
.nvmrc file to their repositories. The file contents is just a simple string representing the version of Node.js the project requires:
A project with this
.nvmrc is specifying that Node.js
v16 should be used. Any developer could then run
nvm use to download, install, and switch to that version. A
nvm install call would then install dependencies in line with that version.
This post is a proof of concept post — the functionality is yet to be perfected. Picture this: you’ve found yourself on a website that uses horizontal scrolling instead of vertical scrolling. It’s an artistic site so you accept that the site scrolls left to right.