fix(js): ignore yarn corepack check when updating config

[AgentEnder]

Current Behavior

Repositories with packageManager set to anything except a valid yarn version will face issues when trying to start the local registry via our verdaccio executor.

Expected Behavior

We can pass SKIP_YARN_COREPACK_CHECK in the env when running commands as part of the verdaccio executor to avoid this issue. We are only ever reading / mutating yarn configs, so its safe in this instance.

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Apr 26, 2024 9:42pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 338b85e. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --targets=e2e,e2e-ci --base=9bf197f5a1610791124a9af6d9a448f72d6f86a8 --head=338b85e1d784a39181349388148a34f0b886ef37 --parallel=1
• nx affected --targets=lint,test,build --base=9bf197f5a1610791124a9af6d9a448f72d6f86a8 --head=338b85e1d784a39181349388148a34f0b886ef37 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=9bf197f5a1610791124a9af6d9a448f72d6f86a8 --head=338b85e1d784a39181349388148a34f0b886ef37
• nx documentation --no-dte
• nx affected -t e2e-macos-ci --parallel=1 --base=9bf197f5a1610791124a9af6d9a448f72d6f86a8 --head=338b85e1d784a39181349388148a34f0b886ef37

---

Sent with 💌 from NxCloud.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.