unicorn/throw-new-error Style

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

What it does

This rule makes sure you always use new when throwing an error.

Why is this bad?

In JavaScript, omitting new (e.g., throw Error('message')) is allowed, but it does not properly initialize the error object. This can lead to missing stack traces or incorrect prototype chains. Using new makes the intent clear, ensures consistent behavior, and helps avoid subtle bugs.

Examples

Examples of incorrect code for this rule:

throw Error("🦄");
throw TypeError("unicorn");
throw lib.TypeError("unicorn");

Examples of correct code for this rule:

throw new Error("🦄");
throw new TypeError("unicorn");
throw new lib.TypeError("unicorn");

How to use

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

CLI

oxlint --deny unicorn/throw-new-error

Config (.oxlintrc.json)

{
  "rules": {
    "unicorn/throw-new-error": "error"
  }
}

References

• Rule Source