Skip to content
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

IE11 parse erroe with standalone.js #61

Open
RaulPampliegaMayoral opened this issue Jun 3, 2019 · 4 comments · May be fixed by #67
Open

IE11 parse erroe with standalone.js #61

RaulPampliegaMayoral opened this issue Jun 3, 2019 · 4 comments · May be fixed by #67

Comments

@RaulPampliegaMayoral
Copy link

Hi all. I'm trying to use the standalone version, but when I try to use it with ie11 tell me that an error occurred parsing the file.
Do you know if there are any problem with this browser?

@egeriis
Copy link
Owner

egeriis commented Jun 11, 2019

It's supposed to be supported by IE11. Unfortunately I didn't introduce the standalone build, so I've never used it myself. Feel free to PR any fix needed!

@RaulPampliegaMayoral
Copy link
Author

Hi @egeriis Luckily with microsoft edge the library is working. This gives me some time to look at the problem. Asap i know something i'll make a pr.

Thanks

@andileco
Copy link

andileco commented Oct 1, 2019

Not sure if this is related, but I was getting a syntax error that pointed to: "var oh = e => e.filename". That seemed to cause an error that prevented other JS (specifically, Highcharts) from working in IE 11, but was fine in Edge and other browsers.

@ianchouinard
Copy link

ianchouinard commented Jan 9, 2020

Running into this issue too. I think the standalone JS build needs to be run through a tool such as Babel to transform the code into something that is "IE friendly". I'm seeing modern JS features such as const and arrow functions that aren't supported in IE.

Edit: Just noticed that this is stated in the docs "you are responsible for transpiling zipcelx for whatever target is relevant for your app"

@codarch codarch linked a pull request Jan 22, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants