← Back to rules

typescript/no-dynamic-delete Restriction

What it does

Disallow using the delete operator on computed key expressions.

Why is this bad?

Deleting dynamically computed keys can be dangerous and in some cases not well optimized. Using the delete operator on keys that aren't runtime constants could be a sign that you're using the wrong data structures. Consider using a Map or Set if you’re using an object as a key-value collection.

Examples

Examples of incorrect code for this rule:

const container: { [i: string]: 0 } = {};
delete container["aa" + "b"];

Examples of correct code for this rule:

const container: { [i: string]: 0 } = {};
delete container.aab;

How to use

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

Config (.oxlintrc.json)

{
  "rules": {
    "typescript/no-dynamic-delete": "error"
  }
}

Config (oxlint.config.ts)

import { defineConfig } from "oxlint";

export default defineConfig({
  rules: {
    "typescript/no-dynamic-delete": "error",
  },
});

CLI

oxlint --deny typescript/no-dynamic-delete

Version

This rule was added in v0.5.2.

References

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