Babel loose mode global variable leakage in class methods

Babel preset-env loose mode global variable leakage

When using @babel/preset-env with the loose option enabled, class constructors and methods can generate code that inadvertently references or pollutes the global scope. This occurs particularly when transforming classes that use static methods or inheritance patterns. The loose optimization bypasses certain runtime checks to produce smaller output, but may create scenarios where variables intended to be scoped locally become accessible globally.

The concern is that this behavior could expose internal state or create side effects that persist beyond the intended execution context. For applications relying on strict scoping or running in sandboxed environments, this leakage could have security or correctness implications. The exact conditions that trigger this leakage—whether specific class patterns, method types, or configuration combinations—require further investigation.

Key areas to examine include how loose mode handles class static initialization, method binding, and prototype manipulation across different ECMAScript features. Which specific class transformation patterns cause global variable leakage in loose mode, and how can developers detect and mitigate this behavior in their build pipelines?