Can the `pnpm setup` command be run after installing pnpm?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.8k
- Forks
- 279
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 2
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the pnpm setup invocation in the standalone installation flow shown from get.pnpm.io/install.sh, then inspect how Corepack installs and launches pnpm. Determine whether setup can run after installation and define completion by confirming the user's shell environment is configured without the reported VSCode ESLint issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100