-
Notifications
You must be signed in to change notification settings - Fork 27k
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
Styled-components FOUC with nextjs and typescript #4782
Comments
Ran into this myself. |
Ooo that's a nice catch, I didn't see that. EDIT: yep, adding |
Ommitting the static keyword happens pretty often. Therefore we should warn the devloper in devmode. Closes: vercel#4782
Omitting the static keyword happens pretty often. Therefore we should trigger a warning in devmode. Closes: vercel#4782
Omitting the static keyword happens pretty often. Therefore we should trigger a warning in devmode. Closes: vercel#4782
Omitting the static keyword happens pretty often. Therefore we should trigger a warning in devmode. Closes: vercel#4782
Omitting the static keyword happens pretty often. Therefore we should trigger a warning in devmode. Closes: vercel#4782
Omitting the static keyword happens pretty often. Therefore we should trigger a warning in devmode. Closes: vercel#4782
Omitting the static keyword happens pretty often. Therefore we should trigger a warning in devmode. Closes: vercel#4782
Omitting the static keyword happens pretty often. Therefore we should trigger a warning in devmode. Closes: vercel#4782
Bug report
Describe the bug
Hi, there seems to be FOUC when attempting to render styled components server-side.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
npm run dev
with the dev tools openstyleTags
prop returns undefinedExpected behavior
I expected style tags to be rendered server side with TS. I ran the same repo without TS, and it behaved as expected.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
Screenshot
Additional Questions
Would this be solved by moving this to _app.js? I don't see anything in the docs that say so. If the examples need to be updated, I'd be willing to do that :)
The text was updated successfully, but these errors were encountered: