PM2 doesnt show which port it uses?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
How can i make it show the port its using? I couldnt find anything.
Please implement PM2 to show the port.
[PM2] Done.
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name │ mode │ ↺ │ status │ cpu │ memory │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 8 │ index │ cluster │ 0 │ online │ 0% │ 76.2mb │
│ 9 │ index │ cluster │ 0 │ online │ 0% │ 80.4mb │
│ 10 │ index │ cluster │ 0 │ online │ 0% │ 77.8mb │
│ 11 │ index │ cluster │ 0 │ online │ 0% │ 76.6mb │
│ 12 │ index │ cluster │ 0 │ online │ 0% │ 69.2mb │
│ 13 │ index │ cluster │ 0 │ online │ 0% │ 64.3mb │
│ 14 │ index │ cluster │ 0 │ online │ 0% │ 63.0mb │
│ 15 │ index │ cluster │ 0 │ online │ 0% │ 48.8mb │
│ 0 │ production │ cluster │ 1 │ online │ 0% │ 73.9mb │
│ 1 │ production │ cluster │ 1 │ online │ 0% │ 74.1mb │
│ 2 │ production │ cluster │ 1 │ online │ 0% │ 73.9mb │
│ 3 │ production │ cluster │ 1 │ online │ 0% │ 73.6mb │
│ 4 │ production │ cluster │ 1 │ online │ 0% │ 74.2mb │
│ 5 │ production │ cluster │ 1 │ online │ 0% │ 73.3mb │
│ 6 │ production │ cluster │ 1 │ online │ 0% │ 73.9mb │
│ 7 │ production │ cluster │ 1 │ online │ 0% │ 74.4mb │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
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
The issue names no file or test; begin at the CLI code that renders the process table shown in the report and trace how each process's metadata is collected. Confirm how PM2 can obtain a listening port, define expected behavior for clustered processes, and verify that the table displays it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100