esm module default ecosystem config name #5451
Description
How could we reproduce this issue?
If I use "type": "module" in packages.json, I need to rename the ecosystem.config,js to ecosystem.config.cjs.
In this case the pm2 start test or pm2 deploy test command not working.
I got the following error message: test environment is not defined in package.json file
I need to specify the ecosystem file name for running. e.g.: pm2 deploy ecosystem.config.cjs test
Please search the default ecosystem.config.cjs filename in esm module mode.
Supporting information
--- PM2 report ----------------------------------------------------------------
Date : Wed Sep 28 2022 17:47:01 GMT+0200 (Central European Summer Time)
===============================================================================
--- Daemon -------------------------------------------------
pm2d version : 5.2.0
node version : 16.17.1
node path : /usr/bin/pm2
argv : /usr/bin/node,/usr/lib/node_modules/pm2/lib/Daemon.js
argv0 : node
user : tgc
uid : 1001
gid : 1001
uptime : 42min
===============================================================================
--- CLI ----------------------------------------------------
local pm2 : 5.2.0
node version : 16.17.1
node path : /usr/bin/pm2
argv : /usr/bin/node,/usr/bin/pm2,report
argv0 : node
user : tgc
uid : 1001
gid : 1001
===============================================================================
--- System info --------------------------------------------
arch : x64
platform : linux
type : Linux
cpus : Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz
cpus nb : 56
freemem : 46305353728
totalmem : 67433533440
home : /home/tgc
===============================================================================
--- PM2 list -----------------------------------------------
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name │ mode │ ↺ │ status │ cpu │ memory │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
===============================================================================
--- Daemon logs --------------------------------------------
/home/tgc/.pm2/pm2.log last 20 lines:
PM2 | 2022-09-22T16:40:59: PM2 log: SIGTERM timeout : 1600
PM2 | 2022-09-22T16:40:59: PM2 log: ===============================================================================
PM2 | 2022-09-28T10:13:32: PM2 log: pm2 has been killed by signal, dumping process list before exit...
PM2 | 2022-09-28T10:13:32: PM2 log: Exited peacefully
PM2 | 2022-09-28T17:04:48: PM2 log: ===============================================================================
PM2 | 2022-09-28T17:04:48: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
PM2 | 2022-09-28T17:04:48: PM2 log: Time : Wed Sep 28 2022 17:04:48 GMT+0200 (Central European Summer Time)
PM2 | 2022-09-28T17:04:48: PM2 log: PM2 version : 5.2.0
PM2 | 2022-09-28T17:04:48: PM2 log: Node.js version : 16.17.1
PM2 | 2022-09-28T17:04:48: PM2 log: Current arch : x64
PM2 | 2022-09-28T17:04:48: PM2 log: PM2 home : /home/tgc/.pm2
PM2 | 2022-09-28T17:04:48: PM2 log: PM2 PID file : /home/tgc/.pm2/pm2.pid
PM2 | 2022-09-28T17:04:48: PM2 log: RPC socket file : /home/tgc/.pm2/rpc.sock
PM2 | 2022-09-28T17:04:48: PM2 log: BUS socket file : /home/tgc/.pm2/pub.sock
PM2 | 2022-09-28T17:04:48: PM2 log: Application log path : /home/tgc/.pm2/logs
PM2 | 2022-09-28T17:04:48: PM2 log: Worker Interval : 30000
PM2 | 2022-09-28T17:04:48: PM2 log: Process dump file : /home/tgc/.pm2/dump.pm2
PM2 | 2022-09-28T17:04:48: PM2 log: Concurrent actions : 2
PM2 | 2022-09-28T17:04:48: PM2 log: SIGTERM timeout : 1600
PM2 | 2022-09-28T17:04:48: PM2 log: ===============================================================================