fnm install --corepack-enabled [VERSION] prevents setting default + aliases at install #1071
Description
Reference:
- Original feature request (Oct 2021): Better Corepack support #566
- Implemented May 2023: allow to automatically enable corepack #960
Docs repeat the following snippet across commands:
--corepack-enabled
Enable corepack support for each new installation. This will make fnm call `corepack enable` on every Node.js installation. For more information about corepack see https://nodejs.org/api/corepack.html
[env: FNM_COREPACK_ENABLED]
- Not sure if it makes sense across all those commands? Especially with the help text of
each new installation. - When used with
fnm install(with--latest/--lts/ or version), default version is not set, nor aliases. Corepack is enabled, but probably should have kept the other expected behaviour.
Reproduction:
$ docker run --rm -it rust bash
$ curl -fsSL https://fnm.vercel.app/install | bash && source ~/.bashrc
$ fnm install --lts --corepack-enabled
Installing Node v20.9.0 (x64)
Enabling corepack for Node v20.9.0
# `default` + `lts-latest` aliases are not set:
$ fnm list
* v20.9.0
* system
# Default version was not set (required to use corepack/node), nor `lts-latest` alias (must now know major version):
$ fnm use 20
# pnpm command is successful (corepack is enabled):
$ corepack prepare pnpm@latest --activate && pnpm --version
8.10.2
$ fnm --version
fnm 1.35.1