microsoft / microsoft/react-native-windows
Explore using PackageReference to Split NuGet Packages by Build Configuration
Open
Nobody has claimed this yet.
Area: Developer Experience
Area: Performance
enhancement
PackageReference
Workstream: New Arch NuGet Refactor
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
This does have some really cool implications for binary distribution package size as well, since we could maybe condition package use on current architecture.
Originally posted by @NickGerleman in https://github.com/microsoft/react-native-windows/issues/8195#issuecomment-876030929
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 reviewing the repository's existing build configurations and PackageReference usage; the issue names no files or tests. Define how package selection should vary by build configuration and architecture, then verify the resulting package contents and build behavior for each configuration.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100