Closed Cedware closed 6 years ago
You can always map aurelia-polyfills to a different library or an empty module.
Any plans on a fix for this?
This also impacts ie11. https://github.com/aurelia/skeleton-navigation/issues/821
No PR in over a year, so closing. Anyone who encounters similar issues, please consider using an alternative polyfill.
I'm submitting a bug report
Please tell us about your environment:
Operating System: Windows 7
Node Version: 7.3.0
NPM Version: 4.0.3
JSPM OR Webpack AND Version webpack 2.5.1
Browser: IE 10
Language: TypeScript 2.3.2
Hello, The library causes a stackoverflow exception with Internet Explorer 10, I will attach a screenshot of the piece of code where the exception occurs. If I deleted the content of the aurelia-poyfills.js and used core-js instead to make sure it's not a failure caused by me. Until this is fixed is there a way to stop aurelia from using the polyfills?
Regarding to the developer console the error is caused at this line:
if (!this || this.constructor !== Collection) return new Collection(a);
Thanks
Cedric