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 small CSS file reset.css to reset all browsers’ default styles that come with the browser’s user agent
People say Impostor Syndrome makes you feel like an intellectual fraud. Are you suffering from this phenomenon?
The best React framework to build admin dashboard which adapts to any backend
Some of the most fundamental concepts which control how CSS is applied to HTML and how conflicts are resolved