Skip to content

Migrate to Yarn Berry (4.18.0) - #626

Open
witchinghourartcollective wants to merge 1 commit into
eth-infinitism:developfrom
witchinghourartcollective:chore/yarn-berry-migration
Open

Migrate to Yarn Berry (4.18.0)#626
witchinghourartcollective wants to merge 1 commit into
eth-infinitism:developfrom
witchinghourartcollective:chore/yarn-berry-migration

Conversation

@witchinghourartcollective

Copy link
Copy Markdown

Summary

  • Pin packageManager: yarn@4.18.0 in package.json and add corepack enable to each CI job, so yarn install deterministically resolves to Berry instead of whatever yarn happens to be on the runner/contributor's machine.
  • Regenerate yarn.lock in Berry's lockfile format. Keep nodeLinker: node-modules in .yarnrc.yml so the install layout stays drop-in compatible with existing tooling (no PnP migration).
  • Ignore Berry's local-only state (.yarn/install-state.gz, etc.) via the standard Berry .gitignore block, while tracking .yarnrc.yml.

This is a tooling/infra change, not a functional one — opening separately from #625 so it can be reviewed/discussed on its own; happy to close if the maintainers prefer to stay on Yarn Classic.

Test plan

  • yarn install (Berry) — resolves and links cleanly
  • yarn compile — passes
  • yarn test — 146/146 passing

Pin packageManager in package.json and enable corepack in CI so
`yarn install` resolves to Berry instead of drifting between Classic
and whatever yarn happens to be globally installed. Regenerate
yarn.lock in Berry format, keep nodeLinker: node-modules for drop-in
node_modules compatibility, and ignore Berry's local-only state
(.yarn/install-state.gz etc.) while tracking .yarnrc.yml.

compile/test verified passing (146/146) against the new lockfile.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant