microsoft / microsoft/react-native-windows
Improve cpp-lib template setup to successfully run yarn automatically at end in CI
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Summary
At the end of the new arch project setup, if dependencies were changed (as happens when adding the example in cpp-lib) we try to run yarn install. This fails in CI for the cpp-lib template added in #12481, probably having to do with the newer version of yarn used by that template.
Motivation
The template setup already fails gracefully if the install ever fails, telling the user to run the install manually instead. The upstream library template also asks the user to run the install manually, so it's not without precedent. But this is only failing in CI, locally the command seems to work find. So while the failing gracefully okay and a good insulation against other unrelated issues that may block the install, we should be able to figure out why the install works locally and make it work in CI too.
Basic Example
No response
Open Questions
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 by inspecting the cpp-lib template setup and the CI job that runs its final yarn install. Compare the CI and local Yarn environments, then verify that the template setup completes dependency installation automatically in CI without requiring a manual install.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100