unicorn/no-thenable Correctness

✅ This rule is turned on by default.

What it does

Disallow then property

Why is this bad?

If an object is defined as "thenable", once it's accidentally used in an await expression, it may cause problems:

Examples

Examples of incorrect code for this rule:

async function example() {
  const foo = {
    unicorn: 1,
    then() {},
  };

  const { unicorn } = await foo;

  console.log("after"); // <- This will never execute
}

Examples of correct code for this rule:

async function example() {
  const foo = {
    unicorn: 1,
    bar() {},
  };

  const { unicorn } = await foo;

  console.log("after");
}

How to use

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

CLI

oxlint --deny unicorn/no-thenable

Config (.oxlintrc.json)

{
  "rules": {
    "unicorn/no-thenable": "error"
  }
}

References

• Rule Source