`pm2.list` does not take effect until after calling `pm2.start`
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?
I use javascript api of pm2. After calling pm2.connect, pm2.list returns an empty array until after calling pm2.start
How could we reproduce this issue?
Supporting information
pm2.connect(err => {
pm2.list((err, apps) => {
console.log(apps) // apps returns an empty array
})
})
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 JavaScript API entry points for pm2.connect and pm2.list, then trace how process state is loaded immediately after connection. Reproduce the empty-array result with the supplied snippet and verify that pm2.list reports the expected processes without requiring pm2.start.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- devops, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100