Skip to content

Migrate from npm to yarn 4.x#12

Open
paoloantinori wants to merge 1 commit into
mainfrom
chore/migrate-to-yarn-4
Open

Migrate from npm to yarn 4.x#12
paoloantinori wants to merge 1 commit into
mainfrom
chore/migrate-to-yarn-4

Conversation

@paoloantinori
Copy link
Copy Markdown

Summary

  • Replaces npm with yarn 4.15.0 as the project's package manager
  • Adds .yarnrc.yml with nodeLinker: node-modules for compatibility
  • Adds packageManager field to package.json
  • Replaces package-lock.json with yarn.lock (root + test-app)
  • Updates all 4 CI/CD workflows to use corepack enable + yarn commands
  • Replaces npm version patch with node scripting in release workflow (yarn 4 has different version semantics)
  • Updates CONTRIBUTING.md and README.md with yarn commands

Test plan

  • yarn install from clean state completes without errors
  • yarn build compiles the library successfully
  • yarn lint passes with zero errors
  • yarn test-app:install && yarn test-app:build builds the test-app
  • CI verify workflow passes (corepack + yarn install --immutable)
  • Review release workflow version bump logic

Closes #1

🤖 Generated with Claude Code

Replace npm with yarn 4.15.0 as the package manager:
- Add .yarnrc.yml with nodeLinker: node-modules
- Add packageManager field to package.json
- Replace package-lock.json with yarn.lock
- Update all CI/CD workflows to use corepack + yarn
- Replace npm version patch with node scripting in release workflow
- Update CONTRIBUTING.md and README.md

Closes #1

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@EricWittmann
Copy link
Copy Markdown
Contributor

Why do we want to migrate from npm to yarn?

@paoloantinori
Copy link
Copy Markdown
Author

No reason. I've just picked up all the open issues I've found. We can certainly ignore this

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.

Update yarn to 4.10

2 participants