-
Notifications
You must be signed in to change notification settings - Fork 5
Switch to Yarn v3 as the package manager default #26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to Yarn v3 as the package manager default #26
Conversation
Related issues in nx which look like they should be fixed before this one can be merged: nrwl/nx#7504 and nrwl/nx#7918. With the other changes in the recent 13.2.3 release, I couldn't figure out the spawnSync issue and related issues that occur when running the e2e tasks using affected. For now, I will be running all of the e2e jobs in sequence and not using affected for the e2e test runs. When running the E2E with this branch, I was getting errors on the package manager install saying that the yarn command failed. |
Nx Cloud ReportCI is running for commit 62b67df. 📂 Click to track the progress, see the status, the terminal output, and the build insights. Sent with 💌 from NxCloud. |
1e60800
to
9b32af8
Compare
@srleecode |
I checked out your branch, ran yarn then the affected e2e and I get this error. I get the same error running yarn e2e. /tmp/nx-e2e --no-interactive --skip-install --collection=@nrwl/workspace --npmScope=proj --packageManager=yarn --preset=empty |
try now... I an using |
Locally it is working. However, on the CI job it failed: https://github.com/srleecode/domain/runs/4353924313?check_suite_focus=true
|
closing as nrwl/nx#7918 was closed |
Yarn v3 has some nice innovations. I am proposing to use Yarn over NPM as the default for this repository and am sending this PR as an example of what we have implemented as a standard at our company. We perform
yarn set version berry
thenyarn set version 3.x
because there is a bug in the stable version.