Don't crash if users mistakingly install babel, webpack, jest, loaders, etc, at the top level
See original GitHub issueI’ve seen this issue multiple times. For some reason people don’t believe react-scripts
is enough and try to install Babel, Webpack, and friends themselves. This can break things.
We need to mitigate this somehow.
Issue Analytics
- State:
- Created 7 years ago
- Comments:28 (16 by maintainers)
Top Results From Across the Web
Issue with babel-jest dependency when running npm start in a ...
I had installed node_modules accidentally in a higher folder. I had: desktop/code/node_modules (remove this to fix); desktop/code/package-lock.
Read more >react-dgrid - npm Package Health Analysis - Snyk
The npm package react-dgrid receives a total of 15 downloads a week. As such, we scored react-dgrid popularity level to be Limited.
Read more >colorful-spin-loader - npm
Start using colorful-spin-loader in your project by running `npm i ... files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your ......
Read more >Files · master · Jonathan Bradley / dashboard · GitLab
A live data dashboard for the University Libraries.
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 Free
Top 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
I think we keep talking past each other. Sorry if I’m being confusing.
I don’t propose to forbid using your own version. (Early wording says that but my more recent comments don’t.)
What I’m saying is we should make sure that installing arbitrary Jest/Babel/Whatever version at top level does not break any of built-in
react-scripts
functionality. So you should be able to use them side by side if you know what you’re doing. In fact that’s how I’d expect it to already work—I have no idea why it breaks (according to reports).Does this clarify things? That’s the only problem I’m referring to in this issue.
Optimally, we want people not to eject. I feel like there’s way too many small things people eject for that’s accomplishable without ejecting (e.g. using
sass-loader
).