← Back to rules

eslint/no-with Correctness

✅ This rule is turned on by default.

What it does

Disallow with statements.

Why is this bad?

The with statement is potentially problematic because it adds members of an object to the current scope, making it impossible to tell what a variable inside the block actually refers to.

It is generally considered a bad practice and is forbidden in strict mode.

This rule is not necessary in TypeScript code if alwaysStrict is enabled.

Examples

Examples of incorrect code for this rule:

with (point) {
  r = Math.sqrt(x * x + y * y); // is r a member of point?
}

How to use

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

Config (.oxlintrc.json)

{
  "rules": {
    "no-with": "error"
  }
}

Config (oxlint.config.ts)

import { defineConfig } from "oxlint";

export default defineConfig({
  rules: {
    "no-with": "error",
  },
});

CLI

oxlint --deny no-with

Version

This rule was added in v0.2.14.

References

• Rule Source
• Upstream rule docs
• Open rule in Oxc Playground