no-dynamic-delete

Disallow using the delete operator on computed key expressions.

🔒

Extending "plugin:@typescript-eslint/strict" in an ESLint configuration enables this rule.

🔧

Some problems reported by this rule are automatically fixable by the --fix ESLint command line option.

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. Using Objects with added and removed keys can cause occasional edge case bugs, such as if a key is named "hasOwnProperty".

Consider using a Map or Set if you’re storing collections of objects.

.eslintrc.cjs

module.exports = {
  "rules": {
    "@typescript-eslint/no-dynamic-delete": "error"
  }
};

Try this rule in the playground ↗

Examples

❌ Incorrect

// Can be replaced with the constant equivalents, such as container.aaa
delete container['aaa'];
delete container['Infinity'];

// Dynamic, difficult-to-reason-about lookups
const name = 'name';
delete container[name];
delete container[name.toUpperCase()];

✅ Correct

const container: { [i: string]: number } = {
  /* ... */
};

// Constant runtime lookups by string index
delete container.aaa;

// Constants that must be accessed by []
delete container[7];
delete container['-Infinity'];

This rule is not configurable.

Options

When Not To Use It

When you know your keys are safe to delete, this rule can be unnecessary. Some environments such as older browsers might not support Map and Set.

Do not consider this rule as performance advice before profiling your code's bottlenecks. Even repeated minor performance slowdowns likely do not significantly affect your application's general perceived speed.

Resources

• Rule source
• Test source