[WCJS] out of stack issue in ie

[Khushboo-chaurasiya]

I am getting out of stack issue in ie but I want to resolve it without using core.min.js

[abergd]

Same here!

[emilio-martinez]

I'm also getting this error, amongst others on IE11.

[MonsieurMan]

I am having the exact same issue.

Stack overflow at line: 78
webcomponents-sd-ce-pf.js (78,288)

[web-padawan]

IIRC this happens because of Symbol polyfill (especially when also using the polyfill from core-js).

[MonsieurMan]

@web-padawan That is exactly my case.
I'm trying to make web components work under Angular and I'm using these polyfills.

I'll update this thread with anything I find.

[kasjerJanusz]

Same here when using these both polyfills:

import '../../../../../node_modules/@webcomponents/webcomponentsjs/webcomponents-bundle.js';
import '../../../../../node_modules/@babel/polyfill/dist/polyfill.js';

When using only one of them, the error doesn't appears.

[web-padawan]

So let me summarise the problem in its current shape:

1. All the "mainstream" ecosystem is using core-js polyfills (which Babel depends on).

2. Philosophy of webcomponentsjs has been always to bring its own polyfills for builtins like Object.assign, Array.from and Symbol to allow using without Babel.

3. Now, two approaches collide because of polyfills are not well tested against one another.

I would highly recommend to reconsider shipping a "bare" polyfill bundle (even though there is already a loader by @open-wc which kinda addresses the same issue).

@sorvell @azakus WDYT ?

[ba55ie]

I also ran into this problem. My temporary fix: Clone this repo and create a custom build which excludes the Symbol polyfill.

[phetw]

@webcomponents/webcomponentsjs@2.1.2 is the latest version that I was able to run Angular 8 on IE11 without this exception.

[Rahulgarg30591]

@MonsieurMan are you able to find anything?

[MonsieurMan]

@Rahulgarg30591, well we finally got a positive response on stopping IE support as we develop internal wep apps only.

@web-padawan and @ba55ie comment are the only thing we can do. It's sad it has not been done as part of this repository.