-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
missing es5
version breaks IE11
#86
Comments
Downgrading to [email protected] fixed the problem for me. Seems to be an acceptable solution since the punycode repo itself states that:
|
@KristiyanVachev I'm having the same problem right now. How did you manage to downgrade the version of punycode, since it's a nested dependency of uri-js? |
I just did. |
Did you install it on project root level or inside the uri-js folder? |
Project root, but my problem wasn't with the instance uri-js had. Uri-js still uses 2.1.0 for the project, but seems like it's not being used. |
Interesting, do you know which part of your application used the wrong version of punycode? Do you have an idea, how I can find the part, which is using |
Are there any plans on implementing this? it is now a huge cause for error on those who use angular build and support ie11. |
Also having the same issue and we need this fixed. |
I was able to fix this by sticking this in my webpack babel-loader config:
|
I'm having the same issue adding [email protected] as a depency did not fix my issue though. It still fails.
|
Same issue. |
same issue |
Lots of packages are dependent from this one. Millions of downloads. And es2015 syntax breaks ie apps. And still not fixed...
Guys, can it be fixed that way? |
If using yarn you can add the following at the bottom of your package.json to force a resolution of version 1.4.1 : |
Hallo Mathias,
while working on my Angular component library eang I realized that [email protected] gets included into my build and since an
es5
version is missing, it is breaking IE11.Not sure why it is needed in the bundle at all, but others seem to have similar issues: angular/angular#21202 (comment)
Would you consider a PR integrating Typescript to transpile to
es5
andes6
?The text was updated successfully, but these errors were encountered: