arguments and options from cli are passed to the forked child process

env: nodejs: v16.14.3 pm2: v5.2.0

I tried to pass the arguments and options to my app script, like the following

pm2 start app.js --no-deamon -- ./entry.js --config ./config/prod.js

If I print process.argv in app.js, the result will be
["start", "app.js", "--no-daemon", "--", "./entry.js", "--config", "./config/prod.js", "./entry.js", "--config", "./config/prod.js"]
(ignore argv[0] and argv[1])

In my situation, the app script is in a npm package, it need a argument and a option to specific its entry and config. It is clear that I get wrong process.argv. My app script launch as
app.js ./entry.js --config ./config/prod.js
Using pm2, it will be
app.js start app.js --no-daemon ...(ignore)

In usually, arguments and options after -- should be ignore in current process and pass to the next process, but pm2 not.

Start by reproducing the reported command with Node.js v16.14.3 and PM2 v5.2.0, then trace the CLI argument parsing and child-process launch path. Done means arguments and options after -- are passed once to the app without PM2's own command arguments appearing in process.argv.