microsoft / microsoft/react-native-windows
Reduce building react-native-windows memory and disk space requirements
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Currently, building a react-native-windows application with some native modules uses a lot of working memory and disk space.
Since native modules for react-native are traditionally developed for Android and/or iOS, we can expect that OSS community members who want to port their modules to react-native-windows will likely use a VM for developing/testing Windows ports. The high memory and disk space requirements can make this a frustrating experience.
We've experience high memory pressure/swapping issues when building react-native-windows applications, most likely due to the C++/winrt codebase, causing OS hangs and failed builds.
A big chunk of free space is also needed for react-native-windows applications build files. After having built react-native-gallery for both Debug and Release, the folder is occupying > 35GB in disk space.
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
Use the react-native-gallery Debug and Release builds described in the issue as a baseline, and investigate which C++/WinRT build outputs or steps drive memory and disk usage. Done means the build uses materially fewer resources while still completing successfully for native-module applications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- build-system, desktop-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100