-
Notifications
You must be signed in to change notification settings - Fork 540
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
Internet Explorer 11 - A valid react element must be returned #238
Comments
@scrambled2k3 did you find a solution to this?? I just ran into the same issue. |
unfortunately no |
@scrambled2k3 Ill let you know what I find. |
+1 works fine everywhere beside IE11 |
+1 |
Did anyone ever find a solution to this? I'm still having this same problem. |
I had some success updating my babel-core and probably more specifically to react 15.5 and it seemed to work that way. If I figure out the exact fix I'll let you know. |
In production builds too or just in development? Can you please provide a demo? |
👋 In case anyone happens on this issue, I wanted to post the fix that I found. This issue in the React repo addresses the issue more generally: facebook/react#8379. The short version, as best I can explain it: React and ReactDOM were loading before babel-polyfill, which led to React's and/or ReactDOM's function for testing the validity of an element not being transpiled properly. Moving babel-polyfill to the first item in my webpack configuration ensured that React and ReactDOM were transpiled properly. The Joyride component is now correctly identified as a valid React element, and the tour is now behaving as expected in IE11, as well as Chrome, Firefox, and Safari. (FYI, the issue was present in both dev and prod builds, and I am using React 15.6.2, Joyride 1.10.1, Webpack 3.5.6, babel-core & babel-polyfill 6.26.0) |
@mchlltt THANK YOU! You saved my production! |
I am getting this error when loading the Joyride component using IE11. Everything works fine in Chrome, Safari and Edge though.
Joyride: 1.10.1
React: 15.5.4
The text was updated successfully, but these errors were encountered: