Getting the console warning: You are loading @emotion/react when it is already loaded.
See original GitHub issueHello, I’m getting warning:
vendor.js:53759 You are loading @emotion/react when it is already loaded. Running multiple instances may cause problems. This can happen if multiple versions are used, or if multiple builds of the same version are used.
../../../node_modules/react-select/node_modules/@emotion/react/dist/emotion-react.browser.esm.js @ vendor.js:53759
Has anyone reproduced the same bug? Any solution?
Thanks in advance 😃
Issue Analytics
- State:
- Created 2 years ago
- Comments:17
Top Results From Across the Web
You are loading @emotion/react when it is already ... - GitHub
You are loading @emotion/react when it is already loaded. Running multiple instances may cause problems. This can happen if multiple versions are used, ......
Read more >React: does not match the corresponding name on disk/ emotion
tsx Cannot find file: 'emotion-react.browser.esm.js' does not match the corresponding name on disk: 'C:\Users\gabrielti\Documents\emasa- ...
Read more >Reactjs — Emotion For Styling Components | by Avery Duffin
This brought about the idea of separation of concerns bring styling out of html and putting it in stylesheets that could be loaded...
Read more >Configure Storybook
By default, Storybook will load stories from your project based on a glob (pattern matching string) in .storybook/main.js that matches all files in...
Read more >FAQs - styled-components
Why am I getting a warning about several instances of module on the page? ... If you are seeing a warning message in...
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
I did look at the
.js
files before, and the string@emotion/react
does not appear anywhere… I will try and produce a replicable case as soon as I have a minute…Hi,
I am still encountering this problem with the latest version of react-select. I tried removing any possible conflicting module, deleted
node_module
andyarn.lock
, and still getting:Relevant parts of
yarn.lock
(and only places@emotion/react
appears):