-
Notifications
You must be signed in to change notification settings - Fork 67
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
IE10 - TypeError: Object doesn't support property or method 'initialise' #88
Comments
Buble@0.15.2 is nearly a year old at this point, have you tried with the latest build (0.18?) |
I will give it a go, but was put off due to this issue. |
Actually, ignore that. I'll just give it a go when I have some time, and will close this issue if the newer version solves my problems. :) |
No luck due to this line in acorn5-object-spread. Will fork and fix. 🙂 |
@nathancahill have opened a pull request that should fix this issue, and will hopefully be merged soon. Then I'll be able to re-test. |
Hi, bublé is currently built to support node 4. You could add other targets in your own build. I'm currently not interested in removing reasonably old JavaScript syntax from acorn5-object-spread, see also browserify/browserify/pull/1794 for a similar discussion. |
@Rich-Harris apparently acorn |
I updated the acorn dependency and removed the plugin in ad7f766. |
@JakeSidSmith I encountered the same problem with styleguidist. Did you fixed this problem? |
@happier2 I'm unsure. I gave up on trying to support IE10 (as we're only using this for internal documentation). Just tried to run in IE10 and now I have some other compatibility errors, which I think are unrelated. |
@JakeSidSmith thanks for your reply. maybe, I should give up too... |
I'm closing this for now. I'll happily merge simple changes that improve bublé compatibility for example with IE 10, but I am not actively checking for anything other than node >= 4. |
Hey there,
I'm using React Styleguidist which uses buble behind the scenes.
It seems that buble is the cause of this issue that was closed a while ago. I believe this only occurs in IE10 (and probably less).
It seems that the cause of the issue is this line, though I'm not entirely sure how this all works.
It may be due to an error in this file, but I haven't had too long to look into this.
Here's a shot of the minified stacktrace.
Additional info:
The text was updated successfully, but these errors were encountered: