Setup a flag to enable writeToDisk in dev mode #7812
Conversation
pupudu
requested review from
ianschmitz,
iansu,
mrmckeb and
petetnt
as code owners
|
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed. If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
|
This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
|
This pull request has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue. Thank you for your contribution! |
About
This PR sets up a flag to enable writing build-files to disk in development mode. As requested by issue #1070. This is quite helpful when using CRA with backends that are not written in JS, when making chrome extensions and when integrating React to a legacy UI system(eg: A UI written in PHP and react components injected in client-side).
These changes are live in a production app (made possible using the npm patch-package module). I believe it makes more sense to make it a built-in feature of CRA.
How to verify changes
react-scripts start --writeToDisk.Documentation and Tests
No tests or docs have been written yet. Happy to make the PR more complete once I get the approval from the maintainers/community.
Disclaimer
This is my 1st PR to CRA. So I apologize if I have made a mistake in the contribution procedure.