emptyFunctions

Reports empty functions that should contain code or a comment.

✅ This rule is included in the ts stylistic and stylisticStrict presets.

Empty functions can reduce readability because readers need to guess whether it’s intentional or not. If a function is intentionally empty, adding a comment makes the intention clear.

Examples

❌ Incorrect

function foo() {}

const foo = function () {};

const foo = () => {};

class Foo {
  bar() {}
}

class Foo {
  constructor() {}
}

✅ Correct

function foo() {
  doSomething();
}

const foo = function () {
  doSomething();
};

const foo = () => doSomething();

function foo() {
  // intentionally empty
}

class Foo {
  bar() {
    /* empty */
  }
}

Options

This rule is not configurable.

When Not To Use It

If you prefer to allow empty functions without comments, you may disable this rule. Some codebases use empty functions as no-ops or placeholders intentionally.

Further Reading

• ESLint no-empty-function
• TypeScript ESLint no-empty-function

Equivalents in Other Linters

• Biome: noEmptyBlockStatements
• ESLint: no-empty-function@typescript-eslint/no-empty-function
• Oxlint: eslint/no-empty-function