nodeのセットアップいつもどうすりゃええんやっけ?ってなるので2023的覚書しておく。
通常 curl -o- <https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh> | bash
でインストールするけど、brewにパッケージ化されてるので、nvmそのもののアップグレードも楽だしbrewで入れる
$ nvm install --lts --latest-npm
$ nvm alias default 'lts/*'
$ nvm current
v18.16.0
$ which node
/Users/okash1n/.nvm/versions/node/v18.16.0/bin/node
$ which npm
/Users/okash1n/.nvm/versions/node/v18.16.0/bin/npm
$ npm list -g
/Users/okash1n/.nvm/versions/node/v18.16.0/lib
├── [email protected]
└── [email protected]
$ nvm ls-remote --lts | tail -n 40
v14.17.5 (LTS: Fermium)
v14.17.6 (LTS: Fermium)
v14.18.0 (LTS: Fermium)
v14.18.1 (LTS: Fermium)
v14.18.2 (LTS: Fermium)
v14.18.3 (LTS: Fermium)
v14.19.0 (LTS: Fermium)
v14.19.1 (LTS: Fermium)
v14.19.2 (LTS: Fermium)
v14.19.3 (LTS: Fermium)
v14.20.0 (LTS: Fermium)
v14.20.1 (LTS: Fermium)
v14.21.0 (LTS: Fermium)
v14.21.1 (LTS: Fermium)
v14.21.2 (LTS: Fermium)
v14.21.3 (Latest LTS: Fermium)
v16.13.0 (LTS: Gallium)
v16.13.1 (LTS: Gallium)
v16.13.2 (LTS: Gallium)
v16.14.0 (LTS: Gallium)
v16.14.1 (LTS: Gallium)
v16.14.2 (LTS: Gallium)
v16.15.0 (LTS: Gallium)
v16.15.1 (LTS: Gallium)
v16.16.0 (LTS: Gallium)
v16.17.0 (LTS: Gallium)
v16.17.1 (LTS: Gallium)
v16.18.0 (LTS: Gallium)
v16.18.1 (LTS: Gallium)
v16.19.0 (LTS: Gallium)
v16.19.1 (LTS: Gallium)
v16.20.0 (Latest LTS: Gallium)
v18.12.0 (LTS: Hydrogen)
v18.12.1 (LTS: Hydrogen)
v18.13.0 (LTS: Hydrogen)
v18.14.0 (LTS: Hydrogen)
v18.14.1 (LTS: Hydrogen)
v18.14.2 (LTS: Hydrogen)
v18.15.0 (LTS: Hydrogen)
-> v18.16.0 (Latest LTS: Hydrogen)
$ mkdir test
$ cd test
$ touch .nvmrc
$ echo "16.20.0" > .nvmrc
$ nvm install
Found '/Users/okash1n/test/.nvmrc' with version <16.20.0>
Downloading and installing node v16.20.0...
Downloading <https://nodejs.org/dist/v16.20.0/node-v16.20.0-darwin-arm64.tar.xz>...
################################################################################################################################################################################################ 100.0%
Computing checksum with shasum -a 256
Checksums matched!
Now using node v16.20.0 (npm v8.19.4)
$ nvm current
v16.20.0