Turbo run never shutdowns cleanly

[openscript]

Summary

I'm on 2.8.9 and running my project with turbo run dev. When I stop the execution with CTRL + C the error ERROR run failed: command exited (1) is shown.

Additional information

How can I cleanly shutdown `turbo run`? When I use `turbo watch` it's even more messy:


@fairaccess/theme:dev: 
^C⠁                                                                                                                                     
>   ...Finishing writing to cache...                                                                                                     WARNING  could not start shutdown, exiting

node ➜ /workspaces/fairaccess (main) $   × Watch interrupted due to signal.

^C
node ➜ /workspaces/fairaccess (main) $ 

What to do?

### Example

https://codeberg.org/fairaccess/fairaccess

[wesleysmyth]

This is expected behavior — when you hit Ctrl+C, turbo sends SIGINT to all child processes and then reports their non-zero exit codes. The ERROR run failed: command exited (1) message is turbo telling you that the child process exited with code 1 (because it received SIGINT).

Why it happens

1. You press Ctrl+C → shell sends SIGINT to the process group
2. Turbo receives SIGINT and forwards it to all child processes
3. Child processes (e.g., next dev, vite) exit with code 1 (or 130)
4. Turbo sees non-zero exit codes and reports them as errors

Suppress the error output

If you just want a clean exit without the error message, handle the signal in your child scripts:

// turbo.json
{
  "tasks": {
    "dev": {
      "cache": false,
      "persistent": true
    }
  }
}

The persistent: true flag tells turbo that this task is long-running and shouldn't be treated as a failure when it exits due to a signal.

With turbo watch

turbo watch handles this differently — it manages the process lifecycle and expects tasks to be restarted. That's why it exits cleanly.

Alternative: Trap signals in your scripts

If you need completely clean shutdown:

// package.json
{
  "scripts": {
    "dev": "node --import ./signal-handler.mjs next dev"
  }
}

// signal-handler.mjs
process.on("SIGINT", () => {
  console.log("Shutting down gracefully...");
  process.exit(0); // Exit with 0 instead of 1
});

When the child exits with code 0, turbo won't report an error.

The real fix: --exit-code flag

Turbo 2.x doesn't have a built-in way to suppress signal-induced exit code errors. The cleanest solution is to accept that Ctrl+C producing an error message is cosmetic — your dev server shut down correctly, turbo just reports the non-zero exit code.

If it truly bothers you, wrap the turbo command:

turbo run dev 2>&1; true

This swallows the non-zero exit code from turbo itself.