PM2 starting flag ```--name or ```name in config will attach ```name on ```process.env``

What's going wrong?

PM2 starting flag --name or name in config will attach ${PM2_APP_NAME} on process.env, which override the original process.env.${OTHER_FRAMEWORK_VARIABLES}, which makes other frameworks or library doesnt properly retrive originals, which maybe loaded from .env and makes it doesnt boot properly (e.g: @nestjs/config)

How could we reproduce this issue?

pm2 start ${APP} --name ${SOME_APP_NAME_OVERRIDE_ENV_VAR}

Possible Solution

use PM2_ prefix when pm2 attaches variable to process.env

Reproduce the issue with the shown pm2 start command and with a name value in config, then trace where PM2 attaches variables to process.env. Done means PM2-specific variables no longer overwrite existing framework environment variables, including the reported @nestjs/config case.