cluster mode can't use nvm chosen version
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
What's going wrong?
when we use nvm use xxx to choose specified node version to run, and use -i 2 to use pm2 cluster mode，the version run node is not the chosen one, but the default version of current machine
How could we reproduce this issue?
Supporting information
$ pm2 report
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 by reproducing the issue with nvm use xxx, then launch PM2 with -i 2 and inspect pm2 report. Compare the Node.js version used by cluster workers with the selected nvm version; done means cluster mode consistently uses the chosen version rather than the machine default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100