You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Warning: Rendering <Context.Consumer.Provider> is not supported and will be removed in a future major release. #47
I was the original poster of the above ghost message and have a bit of an update.
Got things working and if you need a quick fix for now its pretty simple npm install promotively/react-tree-walker or yarn add promotively/react-tree-walker.
We also tried using react-ssr-prepass but had several issues with it (Haven't used it for a while now so its possible that its far more suitable for production than it was, but at the bottom of the readme it still says its not intended for production usage which makes me think otherwise.
I have since migrated our data fetching library package @promotively/react-redux-data towards using the Provider pattern that other libraries such as react-helmet-async use. This is still a solid solution to the problem at hand and is not going to break in future react releases (with the downside of a double render but that's not really a big deal if you are caching SSR pages as you should be anyway)
As far as actual proper suspense support for SSR is concerned - react/react#13206 (Doesn't look like its arriving anytime soon)
Activity
flyon commentedon Sep 12, 2019
bump.. when will the fix in the master be released as a new version on npm? @ctrlplusb
stevenewing commentedon Sep 12, 2019
Hey there,
I was the original poster of the above ghost message and have a bit of an update.
Got things working and if you need a quick fix for now its pretty simple npm install promotively/react-tree-walker or yarn add promotively/react-tree-walker.
We also tried using react-ssr-prepass but had several issues with it (Haven't used it for a while now so its possible that its far more suitable for production than it was, but at the bottom of the readme it still says its not intended for production usage which makes me think otherwise.
I have since migrated our data fetching library package @promotively/react-redux-data towards using the Provider pattern that other libraries such as react-helmet-async use. This is still a solid solution to the problem at hand and is not going to break in future react releases (with the downside of a double render but that's not really a big deal if you are caching SSR pages as you should be anyway)
As far as actual proper suspense support for SSR is concerned - react/react#13206 (Doesn't look like its arriving anytime soon)