pm2 may currupt `[name]` value of webpack's output path

What's going wrong?

pm2 may currupt [name] value of webpack's output path

How could we reproduce this issue?

In some situation, [name] value of webpack's output path may be changed to pm2's process' name value what make webpack bundle result is wrong.

Supporting information

webpack config

pm2 config

run webpack using pm2

bundle error

Please run the following command (available on PM2 >= 2.6)

$ pm2 report

===============================================================================
--- PM2 REPORT (Sun Oct 15 2017 20:05:13 GMT+0800 (中国标准时间)) -------------------
===============================================================================
--- Daemon -------------------------------------------------
pm2d version         : 2.7.1
node version         : 8.6.0
node path            : undefined
argv                 : N:\Program Files\nodejs\node.exe,C:\Users\Diablohu\AppData\Roaming\npm\node_modules\pm2\lib\Daemon.js
argv0                : node
user                 : undefined
uid                  : N/A
gid                  : N/A
uptime               : 13min
===============================================================================
--- CLI ----------------------------------------------------
local pm2            : 2.7.1
node version         : 8.6.0
node path            : undefined
argv                 : N:\Program Files\nodejs\node.exe,C:\Users\Diablohu\AppData\Roaming\npm\node_modules\pm2\bin\pm2,report
argv0                : node

Start by reproducing the reported behavior with the webpack and pm2 configurations shown in the issue, using the supplied pm2 report as environment context. Trace how pm2's process name reaches the webpack invocation and compare the generated output path with the expected [name] value. Done means the bundle output keeps webpack's [name] value when run through pm2.