microsoft / microsoft/react-native-windows
Microsoft.ReactNative nuget packages do not pass NuGet.org health checks
Open
Nobody has claimed this yet.
Area: Developer Experience
bug
Engineering Improvement Candidate
Workstream: New Arch NuGet Refactor
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Problem Description
The NuGet.org NuGet Package Explorer reports the following:
- Source link doesn't appear to pass without the right symbols.
- Determinism doesn't appear to pass (msbuild and/or linker properties we need to set?)
- Compiler flags are missing
Steps To Reproduce
For example, view package explorer: https://nuget.info/packages/Microsoft.ReactNative/0.69.0-preview.6
Expected Results
No response
CLI version
npx react-native --version
Environment
npx react-native info
Target Platform Version
No response
Target Device(s)
No response
Visual Studio Version
No response
Build Configuration
No response
Snack, code example, screenshot, or link to a repository
No response
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 with the NuGet Package Explorer report for Microsoft.ReactNative 0.69.0-preview.6 and review how that package is built and published. Investigate the Source Link symbols, determinism settings, and compiler flags mentioned in the issue; done means the package passes those NuGet.org health checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100