| Release | Status | Initial | Active LTS | LTS Version | Maint LTS | End Of Life |
|---|---|---|---|---|---|---|
| 8 | EOL | 2017-05-30 | 2017-10-31 | 2019-01-01 | 2019-12-31 | |
| 10 | EOL | 2018-04-24 | 2018-10-30 | 10.13.0 | 2020-05-19 | 2021-04-30 |
| 12 | EOL | 2019-04-23 | 2019-10-21 | 12.13.0 | 2020-10-20 | 2022-04-30 |
| 14 | EOL | 2020-04-21 | 2020-10-27 | 14.15.0 | 2021-10-19 | 2023-04-30 |
| 16 | Maint LTS | 2021-04-20 | 2021-10-26 | 16.13.0 | 2022-10-18 | 2023-09-11 |
| 17 | EOL | 2021-10-19 | 2022-04-01 | 2022-06-01 | ||
| 18 | Active LTS | 2022-04-19 | 2022-10-24 | 18.12.0 | 2023-10-22 | 2025-04-30 |
| 19 | EOL | 2022-10-18 | 2023-04-01 | 2023-06-01 | ||
| 20 | Current | 2023-04-18 | 2023-10-24 | 2024-10-22 | 2026-04-30 | |
| 21 | Pending | 2023-10-17 | 2024-04-01 | 2024-06-01 | ||
| 22 | Pending | 2024-04-23 | 2024-10-29 | 2025-10-21 | 2027-04-30 |
node -p "process.versions['v8']"
node --v8-options | grep "in progress" | sortnode --v8-options | grep -v "in progress" | grep harmony | sort
There is no handy way to update node package manager (npm) via the node version manager for windows. Below are the steps to perform the upgrade manually.
- May cause changes to
package-lock.jsonso don't do this unless entire team does as well. If the lock file does change, ensure that any existing branches are also migrated.
nvm use <version to upgrade>cd $NVM_HOME/version to upgrademv npm.cmd npm1.cmd- Delete all remaining npm-related files,
rm -f npm npx.cmd npx npm.ps1 npx.ps1. npm1 install -g npm