microsoft / microsoft/react-native-windows
vnext codegen files deleted and not restored with `yarn build` on Mac
Open
Nobody has claimed this yet.
Area: Build Infrastructure
bug
Mac Development
Workstream: ES Compliance SFI
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Current logic during codegen is to delete all files then generate new ones from source. When running yarn build on a mac (e.g. to test an xplat pacakge), codegen'd headers are deleted, but we silently fail to generate new ones.
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 by tracing the codegen path invoked by yarn build on macOS, focusing on the deletion and regeneration steps described here. Done means generated headers are restored after a macOS build for an xplat package, or that a failure to regenerate is surfaced clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, macos, react-native
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100