-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Object.keys: argument is not an Object in redux-starter-kit.esm.js #152
Comments
Hmm. I'll be honest and say I've put zero thought into browser compat issues so far. That particular chunk of code appears to be a Babel polyfill for the object spread operator. What input and stack trace is leading to that particular edge case getting hit? |
@markerikson , I got this same error today. In your code for configureStore, you are calling _objectSpread. That is where the blow up happens when running on IE11. I tried the react-app-polyfill but it made no difference in this case.
|
Again, to be clear, this is not "our code". That is a Babel build artifact. The actual source is: If someone can come up with a fix and file a PR, I'm open to taking it, but this is a very low priority concern to me atm. |
Closing due to lack of actionable feedback. |
In case anyone comes here via google and is looking for a fix, including the es6-shim resolves the issue. |
Even simpler fix, just set the devTools option to an empty object in the configureStore export default configureStore({
reducer: rootReducer,
devTools: {}
}); |
Hi there,
I'm having an issue using this project with IE11, specifically with this error message in the redux-starter-kit.esm.js file:
The issue occurs in the following method on the third line :
From digging a bit deeper, it seems to try and call
Object.keys
on a value of false, which then fails in IE11.The current behaviour in Chrome is to return an empty array when calling
Object.keys()
on a non-object, but polyfilling IE11'sObject.keys()
method has so far been unsuccessful.Should this starter kit work with IE11 out of the box, or is there some guidance on compatibility?
The text was updated successfully, but these errors were encountered: