Connect to pm2 in no-daemon-mode

[claytercek]

• connects to pm2 in no-daemon-mode
• overrides console methods to use parent logger
• freezes console methods so that pm2 can't override them

Those last two bullets are more of a temporary fix. A better, more permanent solution would be refactoring pm2 to allow for custom loggers instead of using console directly, perhaps by forking the pm2 repo or using patch-package.

Tested with a handful of prod apps, everything seems to be working as expected.

[benjaminbojko]

I did some more testing too and overall this seems great!

One issue I found is that we loose a few of the daemon benefits like single-instance apps:

1. Running launchpad via code (launchpad.startup()) won't make it listen to shutdown signals by default. Because of that, apps aren't terminated on shutdown and subsequent launchpad runs will spawn new app instances. Killing node via taskkill /F /IM node.exe also doesn't kill child processes because they're not handled by a PM2 daemon.
2. Running launchpad in a Windows 11 terminal host (instead of directly via cmd.exe and closing the host (or hitting CTRL+C if launching through a .bat file via explorer) also doesn't close the child processes (also see Window foregrounding and process management failing when Windows 11 default shell is set to Terminal #77 )

The first one was an easy fix: I added a shutdownOnExit option that now automatically listens for onExit within the LaunchpadCore constructor. That can be set to false to disable this behavior. The packages/launchpad/index.js, which is what npx launchpad actually runs, had that as an explicit step, but since we're not running PM2 as a daemon anymore I removed that.

Not quite sure what to do about (2) yet... We may have to look into our own type of daemon options that can register if the main process has terminated. So maybe npx launchpad launches a daemon, that in turn runs LaunchpadCore.startup() (instead of this being directly run via npx launchpad).

[benjaminbojko]

I would say let's merge this change in as it resolve other issues and streamlines the whole stack. I'll create a new ticket for (2).