Jul 13, 2020 • ☕️ 2 min read
Node.js major versions change every 6 months — odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use.
Each release has different set of features and bug fixes, normally LTS version is enough for general use and straightforward to install in all platforms (Linux, MacOS, Windows, etc) and you’ll find yourself upgrade after every 1 or 2 years.
There are situations where the ability to switch between different versions of Node.js can be very useful. For example, if you want to test a module you’re developing with the latest bleeding edge version without uninstalling the stable version of node, develop projects which require different minimum supported Node.js versions.
Before choosing a node version manager, you’ll consider following features:
There are several version managers for node.js. Tools like
n only run on Mac OSX and Linux.
nvm-windows and nodist are designed for Windows
This kind of tool is supposed to enables a concern-free installation and easy switching between different Node.js versions, saving time for what really matters. Better stay away from the one that fails to do so.
A low-level utility-first CSS framework to write inline styles for rapidly building custom user interfaces
You don't know whether Dark Mode is overhyped or necessary but you know there is a real temptation of adding it to your sites
Many companies are adopting monorepo but the decision to use it or not is quite tricky
Monorepo is not new, Google and Facebook have been using it for years. So why now? I believe it depends a lot on the maturity of building systems