Repository navigation
chore(release): version packages - #241
Draft
github-actions[bot] wants to merge 1 commit into
Draft
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
baseballyama
marked this pull request as draft
November 20, 2026 10:46
Member
|
We will release after Svelte Summit 2026. |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
14 times, most recently
from
November 20, 2026 21:46
646dd7d to
d89511c
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 20, 2026 21:49
d89511c to
d836c0b
Compare
This branch has not been deployed
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@sveltejs/vite-devtools-svelte@0.11.1
Patch Changes
#250
0d8c5b2Thanks @baseballyama! - The Build panel's entry badge now comes from Vite's build manifest instead of guessing from file names, and the OG preview no longer stalls the dev server on titles or meta tags with long runs of&.#254
856d5c9Thanks @baseballyama! - The DevTools UI no longer runs a frame loop while the Reactivity graph is hidden, fetches each Reactivity scope once, and stops re-analyzing components on every tree row change (the tree inspector now has a Re-analyze button). A theme picked in the UI now stays when the OS theme changes.#252
6a2bf02Thanks @baseballyama! - The plugin no longer installs@vitejs/devtools-kit. The Vite DevTools dock still needs@vitejs/devtools>= 0.8.0.#245
2b21198Thanks @baseballyama! - The plugin no longer depends onzod; it checks RPC and MCP tool arguments with a small built-in validator. Nothing needs to change.#257
1b01ec6Thanks @baseballyama! - The inspector settings say "Couldn't reset" instead of "Couldn't save" when resetting fails, and inspector warnings and debug output use the[vite-devtools-svelte:inspector]prefix. The package no longer bundlesobug;DEBUG=vite-devtools-svelte:inspectorstill turns on debug output.#244
15f6ae3Thanks @baseballyama! - The MCP server no longer depends on@modelcontextprotocol/sdk, so installing the plugin pulls in about 90 fewer packages. MCP clients get the same tools and answers, so nothing needs to change.#243
13d034dThanks @baseballyama! - MCP tools now answer compact JSON,list_performance_issuesids start with theirkind,get_render_profileuses the same rounded*Msfields asget_component_hotspots(initTimeis nowinitTimeMs), the endpoint answers only POST (405 otherwise), and it reports the package version. The perf skills now ask whether to save a session to disk before ending it, because an ended session cannot be saved later.#253
f89e50bThanks @baseballyama! - The Overview panel now asks the dev server for counts instead of the full module graph and live component list, so opening it and mounting components cost less on large apps.LiveComponentsMetagained afilescount.#240
34e51ceThanks @baseballyama! - The plugin no longer uses thetransformIndexHtmlhook, so SvelteKit stops warning about it (transform_index_html_unsupported). Nothing to change on your side.#247
3239f69Thanks @baseballyama! - The in-page runtime now cleans up bookkeeping for destroyed reactive nodes while DevTools is closed, and spends at most about 1/20 of the main thread serializing a large state that keeps changing.#248
1661a85Thanks @baseballyama! - The package is about a third smaller: it no longer ships source maps or internal type files, and the browser runtime it injects in dev is minified. The plugin's own code is no longer minified, so its stack traces stay readable.