dev-pm

Run npm exec -- dev-pm start <script> for a single script, or use @<group> to start a group defined in dev-pm.config.ts. If the project uses pnpm, use pnpm exec -- dev-pm start instead. Already-running scripts are a safe no-op.

Run npm exec -- dev-pm status to list all scripts, optionally with a pattern to filter. The output shows each script as Running, Waiting, Backoff, or Stopped, plus a restart count indicating past crashes.

The logs command hangs when called without a line limit because it streams output. Always pass -n or --lines <N>, such as dev-pm logs --lines 200 <script>, and never use --follow on start or --interval on status.

Backoff means the process crashed and dev-pm is waiting before respawning, with the delay growing up to 10 seconds. A script flapping in Backoff is broken; read its logs and fix the root cause rather than repeatedly restarting.

No. When a project uses dev-pm, docker compose is typically wired into dev-pm.config.ts as a script, often named docker. Start and stop it through dev-pm, and only bypass it after confirming it is not in the config.

Use shutdown only when explicitly asked to stop everything and kill the daemon, since it halts all scripts and the dev-pm daemon itself. For resetting a single misbehaving service, prefer restart <pattern> instead.