-
Notifications
You must be signed in to change notification settings - Fork 32
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
Support for IE11 #20
Comments
I publish a new version where i upgraded dependencies. let me know if that fix your issue :) |
Unfortunately I missed some packages a long the way 😞 If it's not to much to ask, I'd like for you to publish a new version once these are resolved 😃 |
One of them is already closed and the other seems not in their agenda. |
Is adding https://github.com/SamVerschueren/babel-engine-plugin an option? Or should we do this over at Storybook? |
There is a workaround for this issue until e.g. in your
You may also need to install Babel in your project if it's not already available:
|
🚀 Issue was released in v7.1.2 🚀 |
This addon is really awesome! Unfortunately it isn't working on IE11 😞
The cause for this (there might be more) is
react-element-to-jsx-string
is on version12.0.0
and not13.0.0
(There's a long chain of dependencies here but eventually it uses version
2.0.1
ofget-own-enumerable-property-symbols
which now includes an ES5 compiled version of the code).Not sure if there are any other things that might break IE11, but after disabling just this addon storybook works as expected.
As a workaround - I can take full control over the storybook webpack config and remove the
exclude
from the.js
rule, that excludesnode_modules
, that way every file will go through babel, but that's highly inefficient and might cause other issues when compiling already compiled modules.The text was updated successfully, but these errors were encountered: