setterReturns

Reports return statements with values inside setters.

✅ This rule is included in the ts untyped presets.

The set syntax binds an object property to a function that will be called when there is an attempt to set that property. Setters are expected to have side effects only and not produce a return value. Any value returned from a setter is ignored by the JavaScript engine.

This rule reports when a setter contains a return statement with a value.

Examples

❌ Incorrect

const object = {
  set value(val) {
    return val;
Error ts(2408)  ― Setters cannot return a value.
  },
};

class Example {
  set name(value) {
    return value;
Error ts(2408)  ― Setters cannot return a value.
  }
}

class Example {
  set value(val) {
    if (val > 0) {
      return val;
Error ts(2408)  ― Setters cannot return a value.
    }
    this._value = val;
Error ts(2551)  ― Property '_value' does not exist on type 'Example'. Did you mean 'value'?
  }
}

✅ Correct

const object = {
  set value(val) {
    this._value = val;
Error ts(2551)  ― Property '_value' does not exist on type '{ value: any; }'. Did you mean 'value'?
  },
};

class Example {
  set name(value) {
    this._name = value;
Error ts(2551)  ― Property '_name' does not exist on type 'Example'. Did you mean 'name'?
  }
}

const object = {
  set value(val) {
    if (!val) {
      return;
    }
    this._value = val;
Error ts(2551)  ― Property '_value' does not exist on type '{ value: any; }'. Did you mean 'value'?
  },
};

Options

This rule is not configurable.

When Not To Use It

If you are using an unusual non-standard tool that modifiers your setters at build time into standard functions, this rule may not be for you.

Further Reading

• MDN: setter
• MDN: Object.defineProperty()

Equivalents in Other Linters

• Biome: noSetterReturn
• Deno: no-setter-return
• ESLint: no-setter-return
• Oxlint: eslint/no-setter-return