Can the pnpm setup command be run after installing pnpm?

[liby]

Motivation

The pnpm setup command does the following actions:

• creates a home directory for the pnpm CLI
• adds the pnpm home directory to the PATH by updating the shell configuration file
• copies the pnpm executable to the pnpm home directory

This command is used by the standalone installation scripts of pnpm. For instance, in https://get.pnpm.io/install.sh.

download_and_install() {
  ...
  chmod +x "$tmp_dir/pnpm"
  SHELL="$SHELL" "$tmp_dir/pnpm" setup || return 1
}

If a user is unaware that they need to manually run it after installing pnpm to properly set up environment variables, they may encounter issues such as errors in the VSCode ESLint extension.

[arcanis]

That seems a little out of scope, since it'd perform uncontrolled changes outside of the folders Corepack is supposed to work with. It would also be difficult to make it work once corepack enable isn't explicitly needed.

[liby]

That seems a little out of scope, since it'd perform uncontrolled changes outside of the folders Corepack is supposed to work with. It would also be difficult to make it work once corepack enable isn't explicitly needed.

Hmm, I understand. How about a reminder in the form of a prompt message?

[shellscape]

That seems a little out of scope

It's contextually out of scope by default. But it's absolutely not out of scope for most users of PNPM (hey there, I'm a core contributor to pnpm) who use corepack within CI environments and/or container environments.

This would be useful as an optional executor.