Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Plan for migration to Emotion 10 or styled-components
See original GitHub issueSee https://github.com/emotion-js/emotion/issues/637 for the running Emotion 10 API changes. I think the two that affect us the most are:
-
Apparently function interpolations in
csstagged template literals is going to be deprecated? I didn’t see anything about it in the issue, but got a warning in the console when I tried it recently. -
Static extraction is going to be deprecated entirely. I’m honestly not sure whether/how this affects rendering, but I think the idea is that the
<style>elements are just rendered alongside (hopefully before?) the styled elements rather than going into the<head>, so in theory there wouldn’t be any FOUC.
Alternatively, we could just move over to using styled-components and keep the API we’ve got. ✨
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We might want to wait until Emotion 10 is fully out though so we can weigh the two!
Thanks for pointing that out, @colebemis. It seems like we’d want to do this in a major version regardless, so renaming the prop on our end would be acceptable, IMO. We’d just want to support upgrading it via the codemods from #320 — which, as @emplums relayed to me, were not helpful in getting the Actions UI upgraded because they use TypeScript 😱