We are investigating the frozen-context execution mode, anticipating it will outperform the group-by-origin mode since we currently have a limited number of interest groups in the browser sharing the same joiningOrigin. And we plan to increase the number of Interest Groups cross sites.

However, the frozen-context mode presents several challenges:

1. Bundler Issues: Using a bundler like WebPack generates global variables (e.g., var webpack_modules, function webpack_require(moduleId)), which complicates compliance with "frozen-context" constraints.
2. External Libraries: These libraries make it difficult to adhere to the constraints since we lack control over their code.
3. Unsupported Data Types: Certain data types (e.g., Map, Int32Array) are not supported. While we can implement workarounds in our code, doing so in external libraries is challenging.

Despite its potential performance benefits, our testing indicates that frozen-context is incompatible with third-party libraries and web bundlers.

What options can we explore to address issues related to bundling, external libraries, and unsupported data types in our JS code?