deps: upgrade devframe to v0.9.10 - #556
Merged
Merged
Conversation
…RpcDump
devframe 0.9.10 changed collectStaticRpcDump: its files are now
{serialization, fnName, data} wrappers with per-file structured-clone or
json encoding, and the manifest carries the serialization per entry. The
hand-rolled JSON.stringify loop baked the wrapper objects instead of the
payloads, so the 0.9.10 client could not decode the dump. Delegate to the
shared writeStaticRpcDump helper (the same writer createBuild and buildHub
use) and mirror their connection meta shape (backend + jsonSerializableMethods).
@vitejs/devtools
@vitejs/devtools-kit
@vitejs/devtools-oxc
@vitejs/devtools-rolldown
@vitejs/devtools-vite
@vitejs/devtools-vitest
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
2 participants
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.
Description
Upgrades devframe (and every
@devframes/*package) from^0.9.8to^0.9.10via the shared catalog ref.The bump also required fixing the static-build RPC dump. devframe 0.9.10 changed
collectStaticRpcDump: itsfilesare now{ serialization, fnName, data }wrappers with per-file structured-clone / json encoding, and the manifest carries the serialization per entry. Core's hand-rolledJSON.stringify(data)loop was baking the wrapper objects instead of the payloads, so the 0.9.10 client could not decode the dump. Core now delegates to devframe's sharedwriteStaticRpcDump— the same writercreateBuildand the newbuildHub(#339) use — and mirrors their connection-meta shape (backend+jsonSerializableMethods).Verified end-to-end with a real
cli build: record files now contain real payloads (json fallbacks as plain{inputs,output}; structured-clone records the client decodes via the manifest'sserialization).pnpm typecheck && pnpm test && pnpm lint && pnpm buildall pass.Linked Issues
Follow-up filed upstream to make the new static-hub baker (
buildHub) reusable in Vite DevTools without hand-rollingbuild-static.ts: devframes/devframe#347.Additional context
The remaining
0.8.2/0.9.8entries left inpnpm-lock.yamlcome from a published@vitejs/devtools@0.5.2pulled in transitively by a fixture — pre-existing, unrelated to this bump.This PR was created with the help of an agent.