cleanup-unnecessary-variables

To safely remove redundant variables during code refactoring, you must evaluate each variable to ensure it has no side effects and is not shared, preserving the original evaluation order and behavior.

The best way to inline temporary variables in a JavaScript module is to alias or drop them while enforcing safety rules that prevent accidental removal of side-effectful or shared variables.

Yes, you can apply cleanup to local, non-exported variables in larger projects to reduce code complexity, provided you enforce safety rules to avoid removing variables with side effects.

You should not eliminate unnecessary variables if they produce side effects, are shared across scopes, or if removing them would alter the evaluation order and change the program's behavior.

Variable cleanup reduces code complexity by inlining, dropping, or aliasing redundant local variables, while strictly preserving the original evaluation order and application behavior.