-
Notifications
You must be signed in to change notification settings - Fork 55
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
Upgrade to styled-components v5 #108
Conversation
This pull request is being automatically deployed with Vercel (learn more). gatsby-theme-primer-example – ./🔍 Inspect: https://vercel.com/primer/gatsby-theme-primer-example/577usy82d doctocat – ./🔍 Inspect: https://vercel.com/primer/doctocat/bvx9y6qyp |
Hmmm could someone tell me what made the deployment fail? I don't have permission to access the build logs unfortunately. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking this on, @dcastil! 🎉
It looks like this update broke live preview iframes:
My best guess is that the problem is with the StyleSheetManager
used in the Frame
component: https://github.com/primer/doctocat/blob/master/theme/src/components/frame.js
@mxstbr Did StyleSheetManager
at all in the v5 release?
Damn, I didn't even notice. Thanks for investigating, @colebemis! Seems like some styles are applied and some not. I'll try to figure it out. But there shouldn't be any breaking changes to the |
The |
|
The |
Hi! This pull request has been marked as stale because it has been open with no activity for 60 days. You can comment on the pull request or remove the stale label to keep it open. If you do nothing, this pull request will be closed in 7 days. |
🎉
Release: https://github.com/styled-components/styled-components/releases/tag/v5.0.0
Migration docs: https://styled-components.com/docs/faqs#what-do-i-need-to-do-to-migrate-to-v5