Upgrade examples to use the latest version of emotion
See original GitHub issue- After downloading the mentions example, I get the following error message: Error: The package “react-emotion” has been replaced by “@emotion/styled” in version 10. See https://emotion.sh/docs/migrating-to-emotion-10 for more information on migrating.
- Suggestion: replace the use of such modules by traditional CSS files. This will be much simpler for people like me who come from html+javascript+css. And it works. No hassle.
- In the component:
import './MyComponent.css'
- In MyComponent.css: just plain css
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:13 (4 by maintainers)
Top Results From Across the Web
Emotion 11
Emotion 11 is a slight evolution over the Emotion 10. It focuses mainly on the developer experience, TS types improvements, switches internals to...
Read more >@emotion/react - npm
Latest version : 11.10.5, last published: 2 months ago. Start using @emotion/react in your project by running `npm i @emotion/react`.
Read more >Migrating to Recipe 10
The emotion team have provided some basic tooling to update emotion v9 imports to use the newer emotion v10 packages. This tooling is...
Read more >Saying goodbye to emotion - ezCater
In 2019, the Emotion maintainers shipped a major release of the emotion libraries (v10), adding some very useful new features and updating the ......
Read more >@emotion/styled examples - CodeSandbox
Learn how to use @emotion/styled by viewing and forking example apps that make use of @emotion/styled on CodeSandbox. ; Latest version11.10.5. License ;...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ianstormtaylor : well a bit more than a warning, it stops examples from working. This puts an extra hurdle to mastering and applying the technology. It’s not very encouraging for people who have heard about the power of Slate but are wondering whether it’s worth the effort of taming the beast. OTH the incredible support from the Slate Slack community (https://slate-js.slack.com) makes up for the technical hitches.
I believe that this may be fixed by https://github.com/ianstormtaylor/slate/pull/3093, which has changed a lot of the logic in Slate and
slate-react
especially. I’m going to close this out, but as always, feel free to open a new issue if it persists for you. Thanks for understanding.