Limits of core-js Promise polyfill when global and pure builds coexist
We are designing a hybrid bundle where one entry point relies on the default core-js import to polyfill Promise for legacy browsers, while a separate widget on the same page uses the pure, non-global core-js modules. The goal is to keep both code paths working without one silently overwriting the other. The core-js documentation states that polyfills are app