Importing @pm2/io breaks vscode debugging

[jesobreira]

Hello,

Am working on a codebase that uses @pm2/io for creating processes actions and meters in production.

But seems that simply importing @pm2/io causes this code to route all uncaughtException and unhandledRejection to be routed to pm2, even when the process isn't running on pm2 daemon.

The effect of this, when using VSCode debugging, we lose all the stack trace as it shows as if any error thrown on the codebase was threw by pm2 error handler.

I have commented out the this.catchAll() line on the transpiled/built module and my issues with VSCode debugging were gone.