chore(deps): migrate shared devDependencies to pnpm catalog#478
Merged
Conversation
Contributor
✅ Visual Regression Test ResultsStatus: ✅ All visual tests passed! All screenshots match the baseline. No visual regressions detected! 🎉 |
Contributor
⚡ Performance Benchmark Results✅ Build Time Benchmarks: PASSED❌ Bundle Size Benchmarks: FAILED❌ Runtime Vitals Benchmarks: FAILED📝 Note: Detailed results are available in the job logs. 🎯 Performance Budgets:
Updated: 2026-05-31T22:48:59.008Z |
Contributor
♿ Accessibility Test ResultsOverall Status: ✅ 0/0 tests passed 🦮 WCAG 2.1 AA ComplianceNo WCAG test results available ⌨️ Keyboard NavigationNo keyboard navigation test results available 📊 Detailed ReportDownload the full HTML accessibility report from the workflow artifacts for:
🔍 Testing ChecklistOur accessibility tests verify:
Powered by @axe-core/playwright and Playwright |
Replaces per-package version strings for tsup, vitest, and @types/node with catalog: references defined in pnpm-workspace.yaml. This eliminates version drift across 15 packages and aligns with the approach used in stackwright-pro. - Add catalog section to pnpm-workspace.yaml - Update 15 packages to use catalog: specifiers - Remove tsup, vitest, @types/node from pnpm.overrides - Keep typescript override for transitive enforcement - Keep all security overrides unchanged
perasperaactual
force-pushed
the
chore/pnpm-catalog-migration
branch
from
d7d162d to
f163330
Compare
Contributor
✅ Visual Regression Test ResultsStatus: ✅ All visual tests passed! All screenshots match the baseline. No visual regressions detected! 🎉 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Migrates the OSS repo from
pnpm.overrides-based version pinning to the pnpm catalog approach for shared dev toolchain dependencies, matching the pattern recently adopted in stackwright-pro.Problem
Each package declared its own version ranges for shared devDeps, leading to drift:
tsup:"^8.5.1","^8.5.0","^8.5","^8"vitest:"^4.1.3","^4.0.18","^4"@types/node:"^25.6.2","^25.6"The
pnpm.overridessilently coerced these, but intent was unclear.Solution
catalog:section topnpm-workspace.yaml(single source of truth)"catalog:"specifierpnpm.overridesValidation