chore: update @vitejs/plugin-rsc to 0.5.26#1293
Merged
Merged
Conversation
Collaborator
|
/bigbonk review |
Contributor
There was a problem hiding this comment.
Clean dependency bump. All three touch points are consistent:
pnpm-workspace.yamlcatalog:^0.5.23->^0.5.26packages/vinext/package.jsonpeer dep floor:^0.5.23->^0.5.26pnpm-lock.yaml: all 22 workspace consumers resolve to the single0.5.26snapshot; zero stale0.5.23references remain.
Transitive dep bumps (@rolldown/pluginutils 1.0.0-rc.13 -> rc.18, es-module-lexer 2.0.0 -> 2.1.0) look expected for this release.
LGTM — let CI confirm the full suite passes.
Contributor
|
Review submitted. This is a clean, consistent dependency bump across all three files ( |
commit: |
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
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
Updates the repo-wide
@vitejs/plugin-rsccatalog entry from^0.5.23to^0.5.26, raises the optional peer dependency floor invinext, and refreshes the lockfile so all workspace consumers resolve to0.5.26.This picks up the upstream fix for the public React Server Components advisory covered by
@vitejs/plugin-rsc@0.5.26.Validation
pnpm install --no-frozen-lockfile --ignore-scriptspnpm why @vitejs/plugin-rscreports a single version:0.5.26pnpm test:unit tests/init.test.ts tests/app-router.test.ts tests/request-pipeline.test.ts tests/check.test.ts(246 unit tests;app-router.test.tsis not in the unit project)pnpm test:integration tests/app-router.test.ts(315 integration tests)PATH=/Users/mx/.nvm/versions/node/v24.7.0/bin:$PATH pnpm run fmt:checkPATH=/Users/mx/.nvm/versions/node/v24.7.0/bin:$PATH pnpm run lintpnpm install --frozen-lockfile --ignore-scriptspnpm buildgit diff --checkgitleaks dir /Users/mx/Money/worktrees/hackerone-cloudflare/vinext --no-banner --redact --exit-code 1osv-scanner --lockfile=pnpm-lock.yaml --format=json | jq ...confirmed there are no remaining@vitejs/plugin-rscadvisoriesLocal note: I used Node
v24.7.0for lint and format because my default Nodev22.16.0could not load the TypeScript Vite config. No code changes were needed for that.