-
Notifications
You must be signed in to change notification settings - Fork 3k
Minified file has broken on IE8 #1063
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Karma 1.4.0 indavertantely broke IE8 when updating socket.io. This pins karma to 1.3.0 a version that is known to work on IE8. See karma-runner/karma#2556 See socketio/socket.io-client#1063
Karma 1.4.0 indavertantely broke IE8 when updating socket.io. This pins karma to 1.3.0 a version that is known to work on IE8. See karma-runner/karma#2556 See socketio/socket.io-client#1063
Oh, I thought I looked but I guess I missed that. The "correct" config is |
@darrachequesne Doesn't EDIT: Hmm, that's only a CLI flag, it seems. It's being mapped to |
I tried it, but I think a dependency of socket.io-client is doing something a bit weird that is now failing in the minified version, even with |
Not sure if it helps but since you already run Babel you could try to use babel-preset-es3. |
I believe it didn't help either because it only runs on the current package code :( |
What's weird it that the unminified version currently passes the tests, but even with |
Closed by #1042. |
Sweet, I'll check it out. |
Note: for support questions, please use one of these channels: stackoverflow or slack
You want to:
Current behaviour
Steps to reproduce (if the current behaviour is a bug)
Note: the best way to get a quick answer is to provide a failing test case, by forking the following fiddle for example.
Load up the page in IE8 and notice the error in the console about expecing an identifier

Expected behaviour
No errors
Setup
Other information (e.g. stacktraces, related issues, suggestions how to fix)
I found this because karma 1.4.0 started failing on IE8, the investigation and error lead me to socket.io-client, though, now investigating this it seems like it's potentially deeper that the problem occurs.
This must have happened only recently since karma 1.3.0 still works fine. I tried adding
screw_ie8: false
to the uglify mangle options but it didn't seem to fix it. I'm wondering if some dependency updated to accidentally break IE8 support.Unfortunately, I can't really investigate any longer right now but I'll try to help out as much as I can.
The text was updated successfully, but these errors were encountered: