errorUnnecessaryCaptureStackTraces

Reports unnecessary Error.captureStackTrace() calls in Error subclass constructors.

✅ This rule is included in the ts logical presets.

Calling Error.captureStackTrace() inside the constructor of a built-in Error subclass is unnecessary, since the Error constructor calls it automatically.

Examples

❌ Incorrect

class MyError extends Error {
  constructor() {
    Error.captureStackTrace(this, MyError);
  }
}

✅ Correct

class MyError extends Error {
  constructor() {
    super();
    this.name = "MyError";
  }
}

Optional Chaining

❌ Incorrect

class MyError extends Error {
  constructor() {
    Error.captureStackTrace?.(this, MyError);
  }
}

✅ Correct

class MyError extends Error {
  constructor() {
    super();
    this.name = "MyError";
  }
}

Using this.constructor

❌ Incorrect

class MyError extends Error {
  constructor() {
    Error.captureStackTrace(this, this.constructor);
  }
}

✅ Correct

class MyError extends Error {
  constructor() {
    super();
    this.name = "MyError";
  }
}

Using new.target

❌ Incorrect

class MyError extends Error {
  constructor() {
    Error.captureStackTrace(this, new.target);
  }
}

✅ Correct

class MyError extends Error {
  constructor() {
    super();
    this.name = "MyError";
  }
}

Options

This rule is not configurable.

When Not To Use It

If you’re extending a custom error class that changes the default behavior to not capture the stack trace, you may need to disable this rule for that specific class.

Further Reading

• MDN: Error.captureStackTrace()

Equivalents in Other Linters

• ESLint: unicorn/no-useless-error-capture-stack-trace