Widget `core-js` which interfers with our app

[davidwessman]

Hello.

We are experiencing some issues with a dependency using window.Promise and we have tracked it down to when the Userback-widget assets are included.

Have you changed anything around this recently or is it just some incompatiblity?

[lee-userback]

Yes, we have recently updated to use Webpack 5 to bundle the widget code as well as using core-js as browser polyfills. Are you able to share more details about your issues?

[davidwessman]

We have some other dependencies using Angular which relies on overwriting window.Promise and now there seems to be a race-condition to which implementation is set.

[lee-userback]

Right now, babel is configured for IE11+ where Promise is not yet implemented. So core-js adds window.Promise. The widget code doesn't actually use the native Promise. I will see if we can stop core-js from adding it.

[davidwessman]

Right now, babel is configured for IE11+ where Promise is not yet implemented. So core-js adds window.Promise. The widget code doesn't actually use the native Promise. I will see if we can stop core-js from adding it.

That would be great 🙏

[lee-userback]

Doing some debugging right now, after the widget code is loaded in the browser, window.Promise is the native code instead of a polyfill added by the widget code. @davidwessman are you able to share how you found it was code added by the widget code?

[davidwessman]

I'll try, but will probably be by the end of the week.