chore: migrate to devframe v0.5.2 - #62
Merged
Merged
Conversation
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.
Bumps the workspace catalog from
devframe@^0.4.1to^0.5.2so we pick up the new framework-neutral hub layer introduced in v0.5.0 (devframes/devframe#24). The v0.5.0 release renamed everyDevTools*public type toDevframe*, so this change mechanically updates the affected identifiers (DevToolsNodeContext,DevToolsRpcClient,DevToolsRpcSharedStates) across the server-side RPC wiring and the UI client composable. The stale__VITE_DEVTOOLS_CONNECTION_META__comment inuseRpc.tsis also refreshed to match devframe's renamed global key.This PR was created with the help of an agent.