This repo demonstrates a conflict between babel-polyfill
and aurelia-polyfills
To reproduce, download this repo and start a web server at the root
python -m SimpleHTTPServer 8001
open http://localhost:8001/
In chrome, you can see the success case
And in IE 11 you can see the failure
I have concluded that aurelia-polyfills
has to run first and babel-polyfill
Map
ends up calling into aurelia-polyfills
Collection
in a way causes an infinite loop in aurelia-polyfills
.
I haven't pin pointed exactly where the bug is or which repo is responsible, but I have made an observation
aurelia-polyfills
Collection
appears to assume the constructor isCollection
and if it is not it tries to correct it (src) (but sometimes it isMap
frombabel-polyfill
) src.
- see if anyone on aurelia-polyfills has seen this / has ideas (aurelia/polyfills#31)
- see if anyone on babel-polyfill has seen this / has ideas
- see if I can isolate it to the
Map
polyfill on the babel side that is conflicting with the aurelia side - see if aurelia is polyfilling
Map
(I assume it is) and why babel is also trying to polyfill it - assess work arounds