Can't resolve 'react-select'`
See original GitHub issueAre you reporting a bug or runtime error?
After upgrading to version 3.0.1 I’ve started to receive next error:
Module not found: Error: Can't resolve 'react-select'
What I’ve tried:
- re-install node_modules (also deleting the yarn.lock)
- looked for any breaking changes section in the readme (the only unclear clause was about “UMD builds deprecation” - could you please explain a little more about this? thanks)
- downgrading to 2.4.3 solved the problem
Have you changed any usage flow? What 'm doing is:
import Select, { components } from 'react-select';
Don’t know, if it matters, but I’m using Storybook with a webpack full-control mode (the config can be found here)
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
Module not found: Error: Can't resolve 'react-select'
I got solution by npm i react-select .
Read more >react-select
A Select control built with and for ReactJS. Latest version: 5.7.0 ... Start using react-select in your project by running `npm i react-select`....
Read more >Module not found: Error: Can't resolve 'react-select' with ...
module import is not working for me. I'm tried different solutions provided from stack overflow and other.
Read more >Error: Can't resolve 'react-select' with typescript-Reactjs
I got solution by npm i react-select . Ashwani Panwar 2469. Source: stackoverflow.com. Related ...
Read more >react-select
The Select Component for React.js ... local_offer react-select@5.7.0 ... our DummyInput " since you can't override the DummyInput component with the Styles ...
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
@chulanovskyi @danielsogl @ezzkht this should now resolved in v3.0.3. Thanks for the quick report on the issue
Yeap, that works, thanks!