pm2 list is showing a wrong app version when it executes a script from ecosystem file

What's going wrong?

If you execute pm2 list it does not show the right version for an app in the table:

How could we reproduce this issue?

1. Create a NextJS App.
2. Build the App using next build.
3. Create an ecosystem file:
   module.exports = { apps: [{ name: 'sampleapp', script: 'yarn', args: 'start', // Options reference: https://pm2.io/doc/en/runtime/reference/ecosystem-file/ instances: 1, autorestart: true, watch: false, max_memory_restart: '1G', env: { NODE_ENV: 'development' }, env_production: { NODE_ENV: 'production' } }] }
4. Run pm2 start ecosystem.config.js --dev production
5. Do pm2 list
6. You should see in the table the app version of your package.json file, but pm2 showed version 0.37.0. (I tested it on pm2 4.5.6 and pm2 5.1.0).

Supporting information

$ pm2 report

PM2 | 2021-07-02T10:18:45: PM2 log: App [sampleapp:0] starting in -cluster mode-
PM2 | 2021-07-02T10:18:45: PM2 log: App [sampleapp:0] online
PM2 | ready - started server on 0.0.0.0:8888, url: http://localhost:8888
PM2 | info - Loaded env from /home/usr/sampleapp/.env.local
PM2 | 2021-07-02T10:18:55: PM2 log: Stopping app:sampleapp id:0
PM2 | 2021-07-02T10:18:55: PM2 log: App name:sampleapp id:0 disconnected
PM2 | 2021-07-02T10:18:55: PM2 log: App [sampleapp:0] exited with code [0] via signal [SIGINT]
PM2 | 2021-07-02T10:18:55: PM2 log: pid=43140 msg=process killed

Reproduce the report using the ecosystem.config.js example, a NextJS app, and its package.json, then run the listed pm2 start command followed by pm2 list. Trace how pm2 list obtains the displayed version and make it show the app's package.json version instead of 0.37.0; verify the corrected table output.