No Destructuring

Disallow destructuring patterns to encourage descriptive parameter names and explicit property access.

Summary

The no-destructuring rule reports destructuring patterns in five contexts:

Each check can be independently toggled.

Encourages descriptive parameter names that convey the whole object's role.
Makes property access explicit so readers can trace where each value comes from.
Keeps callback bodies readable with named intermediate constants.

warning

ignoreFiles is an escape hatch for files where this rule genuinely does not apply. It is not intended for routine use.

Option	Type	Default	Description
`assignmentExpressions`	`boolean`	`true`	Ban destructuring in assignment expressions.
`callbackParams`	`boolean`	`true`	Ban destructuring in callback parameters of array methods.
`forOfLoops`	`boolean`	`true`	Ban destructuring in `for...of` loops.
`functionParams`	`boolean`	`true`	Ban destructuring in standalone function/method parameters.
`ignoreFiles`	`string[]`	`[]`	File patterns to skip.
`variableDeclarations`	`boolean`	`true`	Ban destructuring in `const`/`let`/`var` declarations.

Autofix is not available for this rule. Flagged code must be updated manually.

Warning fires on Object.entries() destructuring — The forOfLoops check applies to all for...of destructuring. Access entries by index instead, or set forOfLoops: false.
Want to allow destructuring in variable declarations only — Set variableDeclarations: false while keeping the other checks enabled.