b22914db59
* set engines.node to >=12 * set engines.node to >=12 * Update node-versions.md * update Node.js version in Actions workflows * Update .node-version * Update references to Node.js version from 12 to 14 * Update Dockerfile to use Node.js 14 * set engines.node to safe "12 - 14" range
1.7 KiB
Node Versions
The site currently runs on Node.js v14, the Active LTS version from 2020-10-27 to 2021-10-26.
When updating to a new Node.js version, consider the following files:
- The
engines.nodeentry inpackage.json - The
.node-versionfile used by nodenv, a tool for managing multiple Node.js versions on your machine. - The
.github/*.workflowActions files - The
Dockerfilethat can be used for deployments - The
contributing/development.mdguide - The
contributing/node-versions.mdfile
nodenv
nodenv is a tool for managing multiple Node.js versions on your local machine. It is not required to run this app, but you may already have it installed if you've worked on other projects that use Node.js.
If you're using macOS, run this command to get the latest:
brew upgrade nodenv node-build
If you're using another operating system, or did not use Homebrew to install nodenv, see these upgrade instructions.
To install Node.js 14 and make it your default version, run this command:
nodenv install 14.13.0 && nodenv global 14.13.0
You may sometimes see a warning when running npm scripts with nodenv:
npm WARN lifecycle The node binary used for scripts is [...] but npm is using [...]
This is due to nodenv's overriding behavior. To silence this harmless warning, the nodenv docs recommend running the following command from any directory:
npm config set scripts-prepend-node-path auto