Skip to content
← Back to rules

unicorn/prefer-type-error Pedantic

🛠️ An auto-fix is available for this rule.

What it does ​

Enforce throwing a TypeError instead of a generic Error after a type checking if-statement.

Why is this bad? ​

Throwing a TypeError instead of a generic Error after a type checking if-statement is more specific and helps to catch bugs.

Examples ​

Examples of incorrect code for this rule:

javascript
if (Array.isArray(foo)) {
  throw new Error("Expected foo to be an array");
}

Examples of correct code for this rule:

javascript
if (Array.isArray(foo)) {
  throw new TypeError("Expected foo to be an array");
}

How to use ​

To enable this rule using the config file or in the CLI, you can use:

json
{
  "rules": {
    "unicorn/prefer-type-error": "error"
  }
}
ts
import { defineConfig } from "oxlint";

export default defineConfig({
  rules: {
    "unicorn/prefer-type-error": "error",
  },
});
bash
oxlint --deny unicorn/prefer-type-error

Version ​

This rule was added in v0.0.16.

References ​