Skip to content

chore: use new dedupePeers pnpm option - #2420

Merged
ghostdevv merged 2 commits into
npmx-dev:mainfrom
btea:chore/use-dedupePeers
Apr 9, 2026
Merged

chore: use new dedupePeers pnpm option#2420
ghostdevv merged 2 commits into
npmx-dev:mainfrom
btea:chore/use-dedupePeers

Conversation

@btea

@bteabtea commented Apr 8, 2026

Copy link
Copy Markdown
Contributor

🔗 Linked issue

🧭 Context

📚 Description

refer to https://github.com/pnpm/pnpm/releases/tag/v10.33.0

@vercel

vercelBot commented Apr 8, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
npmx.devReadyReadyPreview, CommentApr 9, 2026 2:13am
2 Skipped Deployments
ProjectDeploymentActionsUpdated (UTC)
docs.npmx.devIgnoredIgnoredPreviewApr 9, 2026 2:13am
npmx-lunariaIgnoredIgnoredApr 9, 2026 2:13am

Request Review

@coderabbitai

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 977c9017-d2f9-4b42-a313-a2d974ea2325

📥 Commits

Reviewing files that changed from the base of the PR and between 526c5db and 604b444.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • package.json
  • pnpm-workspace.yaml

📝 Walkthrough

Walkthrough

The changes update the pnpm tooling configuration in two files. The packageManager field in package.json is updated from pnpm@10.32.1 to pnpm@10.33.0, specifying the version of pnpm for tooling compatibility. Additionally, pnpm-workspace.yaml is modified to include dedupePeers: true, configuring peer dependency deduplication across the workspace. No other project configuration, scripts, dependencies, or settings were altered.

🚥 Pre-merge checks | ❌ 1

❌ Failed checks (1 inconclusive)

Check nameStatusExplanationResolution
Description check❓ InconclusiveThe PR description references the pnpm v10.33.0 release and relates to the changeset, though it lacks detailed context and rationale.Provide more comprehensive context explaining why dedupePeers is being enabled and the impact of upgrading pnpm from 10.32.1 to 10.33.0.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov

codecovBot commented Apr 8, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

@serhalpserhalp left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice, LGTM

@ghostdevvghostdevv changed the title chore: use dedupePeerschore: use new dedupePeers pnpm optionApr 9, 2026
@ghostdevv
ghostdevv added this pull request to the merge queueApr 9, 2026
Merged via the queue into npmx-dev:main with commit ac1fdb3Apr 9, 2026
21 checks passed
@github-actionsgithub-actionsBot mentioned this pull request Apr 9, 2026
ayo-run pushed a commit to ayo-run/npmx.dev that referenced this pull request Aug 5, 2026
Co-authored-by: Willow (GHOST) <git@willow.sh>
Sign up for freeto 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.

3 participants

@btea@serhalp@ghostdevv