Skip to content

chore(release): version packages - #241

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Draft

github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

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 0d8c5b2 Thanks @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 856d5c9 Thanks @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 6a2bf02 Thanks @baseballyama! - The plugin no longer installs @vitejs/devtools-kit. The Vite DevTools dock still needs @vitejs/devtools >= 0.8.0.

  • #245 2b21198 Thanks @baseballyama! - The plugin no longer depends on zod; it checks RPC and MCP tool arguments with a small built-in validator. Nothing needs to change.

  • #257 1b01ec6 Thanks @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 bundles obug; DEBUG=vite-devtools-svelte:inspector still turns on debug output.

  • #244 15f6ae3 Thanks @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 13d034d Thanks @baseballyama! - MCP tools now answer compact JSON, list_performance_issues ids start with their kind, get_render_profile uses the same rounded *Ms fields as get_component_hotspots (initTime is now initTimeMs), 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 f89e50b Thanks @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. LiveComponentsMeta gained a files count.

  • #240 34e51ce Thanks @baseballyama! - The plugin no longer uses the transformIndexHtml hook, so SvelteKit stops warning about it (transform_index_html_unsupported). Nothing to change on your side.

  • #247 3239f69 Thanks @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 1661a85 Thanks @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.

@baseballyama
baseballyama marked this pull request as draft November 20, 2026 10:46
@baseballyama

Copy link
Copy Markdown
Member

We will release after Svelte Summit 2026.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 14 times, most recently from 646dd7d to d89511c Compare November 20, 2026 21:46
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from d89511c to d836c0b Compare November 20, 2026 21:49

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant