pm2-runtime-operator

You can manage specific local PM2 runtimes by applying targeted PM2 commands like start, stop, and restart using a stable process name. This bounded approach ensures safe cleanup and prevents cross-process interference in your local environment.

Yes, you can stream or snapshot logs for a single PM2 process by targeting it with a stable name. This allows precise log collection for specific runtimes without affecting or pulling logs from others.

The best way to safely stop and delete an orphaned PM2 process is using safe teardown patterns with targeted PM2 commands. Name the process specifically to delete it and prevent leaving orphaned processes in the local environment.

Yes, stable process naming is required to inspect and restart PM2 runtimes. A stable name ensures precise, name-based control for lifecycle management and prevents cross-process interference during local development.

Use name-based PM2 process control for local development when you need precise lifecycle management of single-process contexts. It provides safe cleanup patterns and targeted log collection without disrupting other running processes.