CRA & Storybook webpack clash
See original GitHub issueCRA 2.1.5 & Storybook webpack clash - I tried with the latest alpha v of storybook v5.1.0-alpha.25 and the stable version and the problem happens in both
There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"webpack": "4.28.3"
Don't try to install it manually: your package manager does it automatically.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:18
- Comments:74 (23 by maintainers)
Top Results From Across the Web
A dependency conflict between CRA and Storybook
npm start or yarn start throws an error regarding webpack(4.44.2) and/or babel-loader(8.1.0) package. I tried all possible methods listed on ...
Read more >CRA & Storybook webpack clash #6505 - Issuehunt
CRA 2.1.5 & Storybook webpack clash - I tried with the latest alpha v of storybook v5.1.0-alpha.25 and the stable version and the...
Read more >Configure Storybook webpack to work with CRACO override
The main issue is that the react application is utilizing Craco to override the default react configuration. However Craco is also preventing ...
Read more >No Eject - Create React App with SASS, Storybook and Yarn ...
Also, running storybook in the same container as the CRA clashes and this lets you keep an easy separation of concerns / logs...
Read more >@storybook/react | Yarn - Package Manager
@storybook/react. owner storybookjs14.6mMIT6.5.15TS vulns 152 vulnerabilities. Storybook for React: Develop React Component in isolation with Hot Reloading.
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
Hi everyone! Seems like there hasn’t been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don’t have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!
Actually, found a solution: all I had to do was move the
react-scripts
dependency fromdevDependencies
to regdependencies
.