react: cannot set property 'nextEffect' of undefined
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Loading a page produces an error:
cannot set property ‘nextEffect’ of undefined
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/ebsrpraL/).
Unable to replicate the bug in isolation. However, it can be seen on a live page https://go2cinema.com
It is not clear (without knowing React internals) what uses the nextEffect. I have tried using setState, etc. Please advise a plausible test case scenario and I will create a test.
What is the expected behavior?
No error.
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
- React ^16.0.0-rc.2.
- Chrome v25
Note, it is important that Google Chrome v25 works, because otherwise “Fetch as Google” does not work either, i.e. pages are not being indexed, e.g. http://imgur.com/a/phmGU.
See this discussion https://www.reddit.com/r/javascript/comments/6pqrz5/react_16_beta/dkrgvzj/
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 16 (9 by maintainers)
This is a bug in the polyfill you’re using. https://github.com/Financial-Times/polyfill-service/issues/1299
https://github.com/gajus/react-webpack-babel-tutorial/blob/da3eb0f31bd3db888a78e0d16b1ab7e88b82282d/index.html#L8
Just a tip: (Assuming you are using OSX) The best thing to do is to create a new OSX user for installing old chrome. Once downloaded, disable WiFi. Once installed, go straight to settings to disable auto update.
The reason for new OSX user is because two Chrome versions don’t play nice under the same userspace.