Initially I went against creating a separate rehydrate function, because we decided to not actually do rehydration, but instead just regenerate the styles, because it is fast enough and more robust.
So if I did `jss.rehydrate('.style-selector')麓 it would be basically inserting the styles after this element and just removing the old style node.
Now as some people had issues with mismatching selectors from SSR, it makes sense to add some more logic to rehydrate, which will make sure in dev mode that user gets proper error report.
All checks could be done for e.g. if ssr generates a comment string which contains the information (dev mode only). Rehydration call checks the comment and prints a warning or error.
cc @jedwards1211
Indeed, It could be really usefull to have those error reports. Actually managing packages which uses jss as dependency is a pain
Most helpful comment
Indeed, It could be really usefull to have those error reports. Actually managing packages which uses jss as dependency is a pain