microsoft / microsoft/react-native-windows
Bundling should not re-run when no changes to JS files
Open
Nobody has claimed this yet.
Area: Bundle
Area: Developer Experience
enhancement
Workstream: Developer Experience
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
react-native bundle should collect a list of the JS files it traversed and that list fed into the MakeBundle inputs so that we can skip bundling when there are no JS changes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the react-native bundle entry point and trace how MakeBundle inputs are assembled. Identify where traversed JS files can be collected, then verify that unchanged inputs skip bundling while changed files still trigger it. Done means the no-JS-change case avoids re-bundling without affecting normal bundle generation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, javascript, react-native
- Domain
- build-system, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100