-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
"Invalid descriptor for property 'dispatch'" in IE11 #3468
"Invalid descriptor for property 'dispatch'" in IE11 #3468
Comments
Possibly related to this Babel issue? Also, someone just raised a vaguely similar issue with Redux Starter Kit: |
I think it probably is. Guessing the versions of 4.0.2 and 4.0.3 currently on npm were built when those bugs were live in Babel. |
Possibly related issue on react-native |
We ran into this issue today as well. reverting to |
I experience the same problem with "redux": "^4.0.1" |
@wieringen check in your lock file - you probably upgraded without knowing it to |
Ahh yes you are right. :) |
Same issue with native browsers on android 5. |
Looks like they just fixed it yesterday: https://github.com/babel/babel/releases/tag/v7.5.4 I can push a 4.0.4 (error not found?) release using Babel 7.5.4. |
Pushed out 4.0.4 now. Thanks for letting us know! |
Do you want to request a feature or report a bug?
Bug.
What is the current behavior?
With Redux 4.0.2 and up, IE11 throws up an error on load of "Invalid descriptor for property 'dispatch'." The script debugger flags 570,9 in redux.js as the source of the error (which appears to be inside the _objectSpread2(target) function. I don't think this is the source of the error itself as that function exists within previous versions of Redux and seems unchanged between versions. Redux 4.0.1 works fine and does not have this issue.
What is the expected behavior?
Redux works normally as expected.
Which versions of Redux, and which browser and OS are affected by this issue? Did this work in previous versions of Redux?
4.0.2 and 4.0.3 running in IE11 on Windows 10. No other browser seems to be affected. Previous versions (4.0.1 being the most recent) worked.
The text was updated successfully, but these errors were encountered: