noProcessExit (JavaScript)

Language JavaScript (and super languages)

Summary

Diagnostic Category: lint/nursery/noProcessExit
This rule doesn’t have a fix.
The default severity of this rule is warning.
Sources:
- Same as no-process-exit
- Same as n/no-process-exit
- Inspired from unicorn/no-process-exit

How to configure

1
{
2
  "linter": {
3
    "rules": {
4
      "nursery": {
5
        "noProcessExit": "error"
6
      }
7
    }
8
  }
9
}

Description

Disallow the use of process.exit().

In Node.js, process.exit() stops the program right away. Work that is still in progress, such as writing a file, sending a network request, or waiting on a timer, never finishes. The program may also stop without printing why, which makes the problem hard to find.

Throw an error instead. An error that nothing catches also stops the program, and Node.js prints its message and where it happened. To choose the exit code (the number the program reports when it ends, where 0 means success), set process.exitCode and let the program finish on its own.

Examples

Invalid

1
if (somethingBadHappened) {
2
    console.error("Something bad happened!");
3
    process.exit(1);
4
}

code-block.js:3:5 lint/nursery/noProcessExit ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Don't use process.exit().
  
    1 │ if (somethingBadHappened) {
    2 │     console.error("Something bad happened!");
  > 3 │     process.exit(1);
      │     ^^^^^^^^^^^^^^^
    4 │ }
    5 │ 
  
  ℹ It stops the program right away, before work in progress finishes and without saying why it stopped.
  
  ℹ Throw an error instead, or set process.exitCode to choose the exit code.
  
  ℹ This rule belongs to the nursery group, which means it is not yet stable and may change in the future. Visit https://biomejs.dev/linter/#nursery for more information.

Valid

1
if (somethingBadHappened) {
2
    throw new Error("Something bad happened!");
3
}
4

5
if (somethingElseHappened) {
6
    console.error("Something else happened!");
7
    process.exitCode = 1;
8
}