It was a bug in pm2.
I submitted an issue and they fixed it.
To solve it on your side, run these commands:
$ npm install pm2@latest -g
$ pm2 update
And it should work with the latest release.
It was a bug in pm2.
I submitted an issue and they fixed it.
To solve it on your side, run these commands:
$ npm install pm2@latest -g
$ pm2 update
And it should work with the latest release.