← Back to rules

eslint/no-throw-literal Pedantic

💡 A suggestion is available for this rule for some violations.

What it does

Disallows throwing literals or non-Error objects as exceptions.

WARNING

This rule has been deprecated, please instead use typescript/only-throw-error. The typescript rule is more reliable than the Javascript version, as it has less false positive, and can catch more cases.

Why is this bad?

It is considered good practice to only throw the Error object itself or an object using the Error object as base objects for user-defined exceptions. The fundamental benefit of Error objects is that they automatically keep track of where they were built and originated.

Examples

Examples of incorrect code for this rule:

throw "error";

throw 0;

throw undefined;

throw null;

var err = new Error();
throw "an " + err;
// err is recast to a string literal

var err = new Error();
throw `${err}`;

Examples of correct code for this rule:

throw new Error();

throw new Error("error");

var e = new Error("error");
throw e;

try {
  throw new Error("error");
} catch (e) {
  throw e;
}

How to use

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

Config (.oxlintrc.json)

{
  "rules": {
    "no-throw-literal": "error"
  }
}

Config (oxlint.config.ts)

import { defineConfig } from "oxlint";

export default defineConfig({
  rules: {
    "no-throw-literal": "error",
  },
});

CLI

oxlint --deny no-throw-literal

Version

This rule was added in v0.9.10.

References

• Rule Source
• Upstream rule docs
• Open rule in Oxc Playground