Update: claimed by @Alamgird
Now that we have a monorepo structure, we can pull out some of the small and annoying dependencies from packages/react-scripts/package.json into packages/react-dev-utils/package.json and provide helpers there instead.
I started this in #723 but packages/react-scripts/scripts/build.js is still pretty noisy, and we could extract the code to compare build sizes (and maybe something else) into react-dev-utils.
I recommend the following workflow:
- Look at
packages/react-scripts/package.json
- See where these dependencies get used
- If they seem non-essential and too low-level, figure out how to hide them in
react-dev-utils
- Repeat
This is a contributor issue. I don’t plan to work on this right now so please write a comment if you intend to take it. Please don’t start working without a comment so we don’t have many people solving the same problem.
If you need any help, ping me in this issue and I’ll be happy to reply or explain something.
Update: claimed by @Alamgird
Now that we have a monorepo structure, we can pull out some of the small and annoying dependencies from
packages/react-scripts/package.jsonintopackages/react-dev-utils/package.jsonand provide helpers there instead.I started this in #723 but
packages/react-scripts/scripts/build.jsis still pretty noisy, and we could extract the code to compare build sizes (and maybe something else) intoreact-dev-utils.I recommend the following workflow:
packages/react-scripts/package.jsonreact-dev-utilsThis is a contributor issue. I don’t plan to work on this right now so please write a comment if you intend to take it. Please don’t start working without a comment so we don’t have many people solving the same problem.
If you need any help, ping me in this issue and I’ll be happy to reply or explain something.