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
importReactfrom'react'importstyledfrom'@emotion/styled'constDiv=styled.div` color: blue;`exportdefault()=>(<Div><h1>Welcome to React-Static</h1></Div>)
What you did:
Exported the above component using the recommended SSR approach
What happened:
SSR export works and resulting HTML is good! However, during hydration, this error occurs:
Reproduction:
This is using a new alpha build of React-Static v7, so reproduction will be difficult. I understand it may not be fixable until I can provide a replicable setup. Stay tuned as I work on it.
Problem description:
Strangely, the error only happens when NODE_ENV==='production' so I'm not sure what's happening in the production code that would cause this.
Suggested solution:
Not sure yet... :(
The text was updated successfully, but these errors were encountered:
I'm not sure what it does exactly, but after disabling speedy mode as outlined in the docs, everything seems to work. What exactly is speedy doing under the hood?
This issue doesn't contain any concrete repro steps - but the error itself looks really similar to what got reported here - #1468 - and what will be fixed by this - #1572
I might be mistaken of course, but until you provide repro steps I must close this issue due to long inactivity
emotion
version: 10.0.10react
version: 16.8.2Relevant code:
What you did:
Exported the above component using the recommended SSR approach
What happened:
SSR export works and resulting HTML is good! However, during hydration, this error occurs:
Reproduction:
This is using a new alpha build of React-Static v7, so reproduction will be difficult. I understand it may not be fixable until I can provide a replicable setup. Stay tuned as I work on it.
Problem description:
Strangely, the error only happens when
NODE_ENV==='production'
so I'm not sure what's happening in the production code that would cause this.Suggested solution:
Not sure yet... :(
The text was updated successfully, but these errors were encountered: