chore: migrate to pnpm v11

[cwandev]

Summary

Describe the change and why it is needed.

Linked issue

Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

Description

Testing

• pnpm lint
• pnpm --filter base-ui-vue type-check
• pnpm --filter base-ui-vue test
• pnpm docs:build (if docs changed)

Screenshots

Add screenshots, recordings, or visual diffs if they help explain the change.

Checklist

• I linked an issue or discussion.
• I updated tests for behavior changes in packages/core/src/.
• I updated documentation or demos if the change affects public usage.
• I kept the change scoped to one logical improvement.
• I followed the repository's Conventional Commit conventions.

[coderabbitai]

Warning

Review limit reached

@cwandev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 17 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 036709a4-2b5b-4f87-bbd9-e20ed1f17ee5

📥 Commits

Reviewing files that changed from the base of the PR and between fb8977c and 29b68b4.

📒 Files selected for processing (2)

• package.json
• pnpm-workspace.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/pnpm-v10-to-v11

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[pkg-pr-new]

Open in StackBlitz

pnpm add https://pkg.pr.new/base-ui-vue@46

commit: 29b68b4