microsoft / microsoft/react-native-windows
Ensure NuGet package is published before npm package
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Our publish pipeline will publish an npm package for react-native-windows before attempting to build the MSRN binary and publish a NuGet package. If we fail to publish the NuGet package (e.g. due to build stability issues), the resulting npm package would be unusable for binary distribution.
We should ensure a NuGet package is published before publishing the npm package.
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 at the publish pipeline that builds the MSRN binary and publishes the NuGet and npm packages. Trace the publication order and failure handling; done means NuGet publication succeeds before npm publication begins, and a NuGet failure prevents the npm package from being published.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100