microsoft / microsoft/react-native-windows
Consider coalescing community native modules
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
With today's architecture, each native module (that's outside the RNW repo) ends up producing a separate DLL. This could end up creating a large number of DLLs, especially considering the Lean Core effort.
This issue is tracking doing some analysis to determine if a typical RNW app will have too many DLLs, and if so, consider a design for coalescing native modules into fewer DLLs.
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 analyzing the current architecture for community native modules and measuring how many DLLs a typical React Native Windows app produces. Determine whether the DLL count is excessive, then document a design for coalescing native modules into fewer DLLs if needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- build-system, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100