* 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.
* 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>
* feat: simplify EventClient types to accept unprefixed event maps
EventClient now accepts event maps with plain event names instead of
requiring the pluginId prefix in every key. The prefix is handled
purely at runtime. This removes the complex conditional types that
were stripping prefixes from emit/on/createEventPayload signatures.
* ci: apply automated fixes
* chore: add patch changeset for event client type simplification
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* Added CSS Formatting to Enhanced Logs
* Fixed Failing Enhanced Logs Tests
* Added CSS Formatting Test to Enhanced Console Logs
* Added @tanstack/devtools-vite Changeset
* Check for server enviroment in enhanceConsoleLog
- This change is made so log coloring can work in both Server and Browser
- It will use ANSI for Server and CSS for Browser
* fix: make the console logs always conditionally render
---------
Co-authored-by: Alem Tuzlak <t.zlak@hotmail.com>