react-scripts start does not work with lerna run --parallel --stream
See original GitHub issueSince react-scripts 3.4.1 On macos 10.15.3 (not tested elsewhere)
running the command :
yarn lerna run --parallel --stream start
does not start the webpack dev server.
If i remove all lerna arguments it works :
yarn lerna run start
Issue Analytics
- State:
- Created 4 years ago
- Reactions:35
- Comments:12 (1 by maintainers)
Top Results From Across the Web
Lerna & CRA issue "lerna run --parallel start" does not start the ...
The problem is when I execute "yarn start" from root (lerna root) the execution finishes but the site from the second package does...
Read more >Lerna & CRA issue "lerna run --parallel start" does not start the ...
Coding example for the question Lerna & CRA issue "lerna run --parallel start" does not start the devServer-Reactjs.
Read more >Setting Up Monorepo With Create React App - Medium
I found using craco much easier than react-app-rewired. Also we will be using lerna and yarn workspaces to help manage the monorepo. Lets...
Read more >Starting your React project with Monorepo and Lerna — 01
Hello everyone. In this series, I will be talking about how to build React projects with a mono repository approach.
Read more >How To Manage Monorepos With Lerna - DigitalOcean
Without bootstrapping your packages, the package dependencies will not satisfy, and you won't be able to run any npm scripts across the project....
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 have the same issue need rollback to v3.4.0 currently.
Instead of commenting out the line I set
isInteractive
tofalse
, but the issue is still there. SettingCI
env totrue
solves it however.