* fix(devtools-utils): Unmount Preact panels on Preact 11
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* chore(preact-devtools): Develop and test against Preact 11
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* chore(examples): Add px units to numeric Preact styles
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(preact-devtools): Pass the app's context to plugins
The Portal renders plugins into a separate root, so they lost the app's
context (for example QueryClientProvider). Forward the context through
getChildContext. This avoids preact/compat, which patches global options,
and works on Preact 10 and 11.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* ci: stop Release test:lib flakes from runner overload
Release runs nx run-many across every package at nx.json parallel: 5.
That oversubscribes GitHub-hosted runners and flakes two test:lib jobs:
- @tanstack/devtools-ui: default 5s timeout on Solid + goober mounts
- @tanstack/devtools: vitest worker RPC stall (onTaskUpdate)
PR already caps NX_PARALLEL at 3 (#478). Apply the same cap to Release,
and raise the 30s test/hook timeouts on the remaining heavy UI packages.
* chore: upgrade Vitest to v4
Bump vitest from 3.2.4 to 4.1.10. Vitest 4 replaces the 60s
onTaskUpdate RPC timeout that failed Release after every
@tanstack/devtools test had already passed.
Migrate defineWorkspace to test.projects. Turn off Solid HMR in
tests so the module runner does not load /@solid-refresh. Update
mocks and timers that Vitest 4 types or isolates differently.
* docs: add Svelte devtools adapter design doc
* docs: add Svelte devtools implementation plan
* feat(svelte-devtools): add Svelte 5 adapter package
* feat(devtools-utils): add Svelte factory functions and build config
* fix: resolve knip issues and update svelte vite plugin to v6
* docs: add Svelte documentation
* chore: add changeset for Svelte adapter
* ci: apply automated fixes
* fix(svelte-devtools): mount once and tear down stale plugin components on update
- Mount the core exactly once: untrack props in the mount $effect so a prop
change no longer destroys and rebuilds the entire devtools core (the update
$effect already handles config/plugin changes reactively).
- update() now calls destroyAllComponents() before setConfig(), matching the
Angular adapter — the core re-invokes render/name for the new plugin set, so
without this the previous Svelte instances were orphaned and leaked.
- renderComponent() keys mounted components by container.id directly (the core
always assigns one) instead of an empty-string fallback that could never be
matched on destroy.
- vite.config: cast svelte() plugin as any, matching the vue/solid configs, to
satisfy the vite 8 plugin types.
* chore(devtools-utils): add svelte devDependency for the svelte subpath build
The `./svelte` build type-checks svelte-importing source, so svelte must be
resolvable at build time (mirroring vite-plugin-solid for the solid build)
rather than relying on workspace hoisting of the optional peer.
* test(devtools-utils): cover svelte plugin and panel factories
Mirrors the existing solid class factory tests: createSveltePlugin shape +
NoOp behavior, and createSveltePanel mounting/tearing down a class-based core.
* ci: apply automated fixes
* refactor(devtools-utils): make createSveltePlugin generic over component props
Threads a TComponentProps generic through the svelte plugin factory (mirroring
createVuePlugin) so plugin props are type-checked against the component instead
of falling back to `any`. Addresses PR review feedback.
* ci: apply automated fixes
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Adds the `bugs` field pointing to the GitHub issue tracker to every publishable package under packages/. This was the only standard metadata field missing; repository, license, homepage, funding, author and keywords were already present and consistent across all packages.
* fix: include skills/ and bin/intent.js in npm publish for all packages
The skills/ directories and intent bin shim were missing from the
individual package.json files. The intent scanner requires both
"bin": { "intent": ... } and a skills/ directory to detect packages.
Without these, npx @tanstack/intent install reports "No intent-enabled
packages found."
* ci: apply automated fixes
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* fix(devtools): prevent solid-js from leaking into server bundles
Move all solid-js runtime imports (render, Portal, lazy, ClientEventBus)
from core into a new mount-impl.tsx file loaded via dynamic import().
This ensures solid-js code is never in the static import graph and only
loads as a separate chunk when mount() is called on the client.
* feat(devtools-utils): add Solid.js support and enhance routing configurations
* ci: apply automated fixes
* fix(devtools-utils): resolve self-referencing import for clean CI builds
Add ambient module declaration (barrel-types.d.ts) so TypeScript can
resolve @tanstack/devtools-utils/solid on clean checkouts without dist/.
* ci: apply automated fixes
* fix(devtools-utils): fix lint errors in solid class files
* fix(devtools-utils): use variable import path to prevent esbuild SSR pre-bundling
esbuild follows dynamic imports with string literals during Vite's
dependency optimization, pulling solid-js into the SSR bundle. Using a
variable path prevents static analysis from following the import.
* fix(devtools-utils): add workerd export condition to ./solid for Cloudflare SSR
The ./solid export was missing a workerd condition, causing Vite's SSR
dep optimizer (esbuild) to resolve to the client entry instead of
server.js when running under Cloudflare workerd. The client entry's
compiled Solid JSX imports use/setStyleProperty from solid-js/web which
don't exist in the server entry, crashing the dev server.
Also reverts the variable import workaround in class.ts back to a
literal import, since the workerd condition now properly routes SSR
resolution to the server entry.
* Refactor code structure for improved readability and maintainability
* fix(devtools-utils): use relative dynamic import for class-mount-impl
Replace the cross-package bare specifier import('@tanstack/devtools-utils/solid')
with a relative import('./class-mount-impl'). Bare specifiers in dynamic imports
inside pre-bundled dependencies aren't resolved by bundlers like esbuild/webpack,
causing "Failed to resolve module specifier" errors in the browser.
The relative import works in all bundlers (Vite, Next.js, etc.) because the
class-mount-impl.js file is co-located in the same dist directory, built
together via a single vite config with vite-plugin-solid for JSX compilation.
* ci: apply automated fixes
* chore: fix issues
* chore: changeset
* fix: lock
* ci: apply automated fixes
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* fix: make the import meta conditional to work outside of vite
* ci: apply automated fixes
* changeset
* fix: unmounting of devtools
* fix: unmounting of devtools
* ci: apply automated fixes
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
This PR was opened by the [Changesets
release](https://github.com/changesets/action) 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
## @tanstack/devtools-utils@0.0.3
### Patch Changes
- fix issues with mounting
([#171](https://github.com/TanStack/devtools/pull/171))
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>