-
Notifications
You must be signed in to change notification settings - Fork 154
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
React 16.6.0 bug #32
Comments
after additional investigation, I found that problem is actually in react-async-component. Closing PR as not relevant |
@dlebedynskyi Any suggestions on how you fixed the issue? Running into it myself |
@mschipperheyn Core issues for me was null passed to provider on SSR. that was a bug in react-async-component. |
I did the same and I still have the same error :-( The error is caused I think by |
You should reference ctrlplusb/react-async-bootstrapper#14 |
Similar issue:
|
@aseem2625 I am also facing the same issue. Did you find any solution? Thank you for any help. |
There seems to be an issue with react 16.6.0 -1 context api on server side render
getting following errors during render
TypeError: Cannot read property 'helmetInstances' of undefined
Dispatcher.js:70 Dispatcher.init
[id-portal-web]/[react-helmet-async]/lib/Dispatcher.js:70:48
Dispatcher.js:116 Dispatcher.render
[id-portal-web]/[react-helmet-async]/lib/Dispatcher.js:116:12
return _react2.default.createElement(
_Provider.Context.Consumer,
null,
function (context) {
// 👇 here
return _react2.default.createElement(_Dispatcher2.default, _extends({}, newProps, { context: context }));
}
);
The text was updated successfully, but these errors were encountered: