The easiest way to manage Node.js / npm on Linux is by using the Node Version Manager:
https://github.com/nvm-sh/nvm
I. Install NVM
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
II. Use NVM to install the latest LTS release of Node.js / npm
nvm install --lts
III. List versionsnvm ls
This will output a mix of both installed and available versions (including all LTS releases)
N/A
default -> lts/* (-> N/A)
iojs -> N/A (default)
node -> stable (-> N/A) (default)
unstable -> N/A (default)
lts/* -> lts/iron (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.12 (-> N/A)
lts/fermium -> v14.21.3 (-> N/A)
lts/gallium -> v16.20.2 (-> N/A)
lts/hydrogen -> v18.19.0 (-> N/A)
lts/iron -> v20.10.0 (-> N/A)
When installing and uninstalling specific versions, you can use both the numeric version, or the release designation (e.g. v16.20.2 and lts/gallium are interchangeable)
IV. Uninstall a specific version
nvm uninstall lts/iron
V. Install a specific version
V. Install a specific version
nvm install lts/hydrogen
VI. Use a specific version
nvm use lts/gallium
If you're running an older version of Linux, you may only have access to older Node.js versions, because a dependency on the GNU C Library (glibc).
Trying to run anything newer than lts/gallium on Amazon Linux 2 will throw the following:
node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by node)
node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by node)
You can update the NPM version independently from Node.js, but this too has a limit. Gallium comes with version 8. At the time of this writing, it prompts that version 10 is available, but you can only upgrade up to version 9.
npm install -g npm@9
(It will complain about incompatible versions if you try to install version 10).
No comments:
Post a Comment