PM2 CLI Config File Name/Reference Anomaly

What's going wrong?

PM2 CLI Config File Name/Reference Anomaly

Expectation that PM2 Config File may be named anything and outcome is same.

Filesystem

+ Project
  - config.ecosystem.cjs
  - ecosystem.config.cjs

Filesystem Content

module.exports = {
  apps: [
    {
      name: "DFC-Configurator-Docubase",
      script: "./index.js",
      watch: [
        "./index.js",
        "./package.json",
        "./config/**/*.*",
        "./pilers/**/*.*"
      ],
      args: "--config ./config.docubase.json",
      node_args: "--inspect=127.0.0.1:9231",
      execMode: "fork"
    }
  ]
}

CLI Commands

Unexpected (config.ecosystem.cjs)

Input

pm2 start ./config.ecosystem.cjs

Output

0  │ config.ecosystem    │ default     │ 1.0.0  

Resolve
Application does not start.

Expected (ecosystem.config.cjs)

Input

p2 start ./ecosystem.config.cjs

Output

0  │ DFC-Configurator-Docubase    │ default  

Resolve
Application starts.

Supporting information

• Node: 22.4
• PM2: 5.4.1

Reproduce the two commands with config.ecosystem.cjs and ecosystem.config.cjs using the supplied PM2 and Node versions, then trace the CLI handling of ecosystem configuration filenames. Done means both filenames load the apps entry and start DFC-Configurator-Docubase rather than treating the filename as the application name.