Get forked react-scripts changes to take effect immediately
See original GitHub issueI have forked CRA, made some alternations to Webpack config and yarn link
it to a project. after starting the project yarn start
and then making some changes again to the configs, it doesn’t take effect immediately. I have to stop the project and run yarn start
again and again, I really need this for debugging purpose and I’m looking for it for a week now, supposedly there was a workaround that doesn’t seem to match the current version of react-scripts. no any other information I could find in the docs or CONTRIBUTING.md.
any workarounds??
ver: react-scripts@3.0.1
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Power up create-react-app! - DEV Community
In this post, I will walk through creating both a custom react-scripts fork and a custom CRA template, and I will compare both...
Read more >Don't eject your Create React App | by Adam Laycock - Medium
Rather than ejecting and maintaining the build process yourself, forking react-scripts allows you to make changes while also reusing it on ...
Read more >Fork and install Create React App without publishing on NPM
All tutorials on the subject publish the forked repo to NPM to install via the normal way.
Read more >Forking instead of Ejecting a Create React App - YouTube
We will fork facebook's `create-react-app` repo and modify its ` react - scripts ` to make your own version that you can publish...
Read more >Overriding the Create-React-App Webpack Configuration ...
So... how can we change this configuration without ejecting create-react-app (or worse, forking react-script )? ...
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
The request was made at the time version 2 was the most recent version, but the last comment stated they are planning to support it: https://github.com/webpack/webpack-cli/issues/15#issuecomment-544137722.
If they are related to webpack, yes.
the issue you point out is for Webpack v2, create-react-app uses Webpack v4 and it already supports watch mode and dev-servers. also, I found out there is dev server config in the CRA. but no explanation what so ever. so, is there any use for this file?
I mean when do you
npm start
to work on a new feature that needs Webpack change, do you restart it every time to see the change?