Overview - Devtools

devtools

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
main
d6e9022a feat: add @tanstack/devtools-rspack (1:1 Vite parity) + shared @tanstack/devtools-bundler-core (#484) * feat(bundler-core): scaffold @tanstack/devtools-bundler-core package * feat(bundler-core): move framework-agnostic logic out of devtools-vite * feat(bundler-core): add dev-state singleton for loader/plugin sharing * refactor(devtools-vite): consume @tanstack/devtools-bundler-core * test(bundler-core): relocate handleDevToolsRequest routing tests from devtools-vite * feat(devtools-rspack): scaffold package with skeleton exports * feat(devtools-rspack): transform pipeline loader * feat(devtools-rspack): plugin (loader injection, event bus, dev middleware, package manager) + dev-server port routing * chore(devtools): fix core import ordering + guard rspack package-manager wiring in CI * test(devtools-rspack): entry factory test * test(devtools-rspack): react rspack example + e2e smoke * chore: changesets for devtools-bundler-core + devtools-rspack Also removes the redundant @rspack/core devDependency from devtools-rspack (already declared as peerDependency, unused otherwise per knip). * fix(devtools-rspack): process @tanstack node_modules for connection placeholder + runtime-bridge injection The single loader rule excluded all of node_modules, so the __TANSTACK_DEVTOOLS_* connection placeholders (which live in @tanstack/devtools-event-bus's client, under node_modules for real consumers) were never replaced -- breaking a custom eventBusConfig.port/host/protocol. Add a second loader rule scoped to @tanstack/devtools*|event-bus* under node_modules (flat + pnpm nested layouts), and normalize the step-4 id gate to posix so it matches on Windows. Matches vite's connection-injection, which does not exclude node_modules. * fix(devtools-rspack): eager event-bus connection, gate dep-refresh on package.json, port-routing tests, doc accuracy * fix(devtools-rspack): emit package-json-read on package.json change (vite parity) * chore(devtools): formatting + lint fixes * fix(devtools-rspack): make marketplace + go-to-source work under Rspack - Seed the shared global event target before wiring the package manager so the plugin receives the client's `mounted` event and replies with `package-json-read` (the marketplace stayed empty without it), and gate the wiring on the compiler mode instead of `process.env.NODE_ENV`, which isn't set at `apply()` time under `rspack serve`. - Normalize the module path before stripping cwd in enhance-logs and inject-source so Rspack's backslash ids on Windows don't leak an absolute path that breaks editor open. - Enable `connectToServerBus` in the react-rspack example so the client connects to the event bus. * ci: apply automated fixes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Alem Tuzlak
Succeeded
feat/devtools-rspack
4edbf313 fix(devtools-rspack): make marketplace + go-to-source work under Rspack - Seed the shared global event target before wiring the package manager so the plugin receives the client's `mounted` event and replies with `package-json-read` (the marketplace stayed empty without it), and gate the wiring on the compiler mode instead of `process.env.NODE_ENV`, which isn't set at `apply()` time under `rspack serve`. - Normalize the module path before stripping cwd in enhance-logs and inject-source so Rspack's backslash ids on Windows don't leak an absolute path that breaks editor open. - Enable `connectToServerBus` in the react-rspack example so the client connects to the event bus.
by Alem Tuzlak
Succeeded
main
d061f0cc feat(devtools): add floating/draggable trigger with throw physics (#485) * feat(devtools): add floating/draggable trigger with throw physics Add a `triggerMode: 'fixed' | 'floating'` setting. In floating mode the trigger can be dragged anywhere with the left mouse button; releasing with velocity throws it (inertia + wall bounce). Position is clamped to a padded on-screen area (matching the fixed trigger's edge offset) and persisted to local storage, re-clamping on window resize so it can never load off-screen. * ci: apply automated fixes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Alem Tuzlak
Succeeded
feat/draggable-trigger
daf4648b Merge 6bee559dac9dd249ea42e020bb78dbbce76050ad into 92f69d014a981518915064593adc7bb4ffb71f3a
by Alem Tuzlak
Succeeded
feat/devtools-rspack
51bc1dae chore(devtools): formatting + lint fixes
by Alem Tuzlak
Succeeded
main
92f69d01 ci: stabilize flaky Test job (cap nx parallelism + raise vitest timeouts) (#478) * test(devtools): raise vitest timeouts to stop flaky component test:lib in CI The component tests added in #472 render the full Solid + goober tree and take 1-4s locally. Shared CI runners are ~4x slower (the suite runs in ~8s locally but ~31s in CI), which pushes individual tests past vitest's default 5s testTimeout and causes intermittent `@tanstack/devtools:test:lib` failures across unrelated PRs (e.g. #471, #477). Raise testTimeout and hookTimeout to 30s for the devtools package so slow CI runs have headroom. Fast unit tests are unaffected; a real hang still fails (just after 30s instead of 5s). * ci: cap nx parallelism to 3 to fix flaky Test job nx.json sets `parallel: 5`, which is fine for local dev machines but oversubscribes GitHub-hosted runners: each affected `test:lib` (vitest) and `test:types` (tsc) task spawns its own worker pool, so 5 heavy tasks at once exhaust CPU/RAM and intermittently stall or OOM-kill deterministic tasks. That produced flaky failures across unrelated PRs (#471, #477, #478) that pass on a plain re-run. The team already pins `test:e2e` to `--parallel=1` for the same reason; cap the Test job's nx parallelism via NX_PARALLEL=3 (CI-only, leaves local dev at 5). Combined with the raised vitest timeouts, this keeps tasks within the runner's budget.
by Alem Tuzlak
Succeeded
fix/stabilize-devtools-component-test-timeouts
772d3ada ci: cap nx parallelism to 3 to fix flaky Test job nx.json sets `parallel: 5`, which is fine for local dev machines but oversubscribes GitHub-hosted runners: each affected `test:lib` (vitest) and `test:types` (tsc) task spawns its own worker pool, so 5 heavy tasks at once exhaust CPU/RAM and intermittently stall or OOM-kill deterministic tasks. That produced flaky failures across unrelated PRs (#471, #477, #478) that pass on a plain re-run. The team already pins `test:e2e` to `--parallel=1` for the same reason; cap the Test job's nx parallelism via NX_PARALLEL=3 (CI-only, leaves local dev at 5). Combined with the raised vitest timeouts, this keeps tasks within the runner's budget.
by Alem Tuzlak
Succeeded
fix/stabilize-devtools-component-test-timeouts
be847bbc ci: cap nx parallelism to 3 to fix flaky Test job nx.json sets `parallel: 5`, which is fine for local dev machines but oversubscribes GitHub-hosted runners: each affected `test:lib` (vitest) and `test:types` (tsc) task spawns its own worker pool, so 5 heavy tasks at once exhaust CPU/RAM and intermittently stall or OOM-kill deterministic tasks. That produced flaky failures across unrelated PRs (#471, #477, #478) that pass on a plain re-run. The team already pins `test:e2e` to `--parallel=1` for the same reason; cap the Test job's nx parallelism via NX_PARALLEL=3 (CI-only, leaves local dev at 5). Combined with the raised vitest timeouts, this keeps tasks within the runner's budget.
by Alem Tuzlak
Succeeded
fix/stabilize-devtools-component-test-timeouts
1cdbd5b1 test(devtools): raise vitest timeouts to stop flaky component test:lib in CI The component tests added in #472 render the full Solid + goober tree and take 1-4s locally. Shared CI runners are ~4x slower (the suite runs in ~8s locally but ~31s in CI), which pushes individual tests past vitest's default 5s testTimeout and causes intermittent `@tanstack/devtools:test:lib` failures across unrelated PRs (e.g. #471, #477). Raise testTimeout and hookTimeout to 30s for the devtools package so slow CI runs have headroom. Fast unit tests are unaffected; a real hang still fails (just after 30s instead of 5s).
by Alem Tuzlak
Failed
fix/stabilize-devtools-component-test-timeouts
1cdbd5b1 Merge aaa71f660f6aabe405de14ba266c8f41d4e4597d into e0266670c895303ae80ceaa1d35d8d3da49f34c2
by Alem Tuzlak
Succeeded
main
b1ac893a feat(event-client): strip the root EventClient export from production by default (#471) * feat(event-client): add shared types module, /production entry, and package wiring * feat(event-client): add standalone no-op client and share event types * feat(event-client): no-op the root export outside development * docs(event-client): document dev-only root export and /production subpath * chore(event-client): add changeset for production stripping * test(event-client): guard no-op/real public-surface parity and cover the dev resolver branch * docs(event-client): clarify unset NODE_ENV behavior and fix stale stripping guidance * ci: apply automated fixes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Alem Tuzlak
Succeeded
feat/event-client-production-stripping
afd8f8e8 fix(devtools): rename Solid use* primitives to create* for React Compiler compat (#477) * fix(devtools): rename Solid use* primitives to create* for React Compiler compat The devtools packages are Solid but used React-style naming (useStyles, useTheme, useDevtoolsState, ...) for their custom primitives. When an app enables React Compiler, it matches the use* convention and transforms this Solid code as if it were React, breaking the panel. Rename every custom Solid primitive in @tanstack/devtools, devtools-ui, and devtools-a11y from use* to create*, and import Solid's useContext and @solid-primitives' useKeyDownList under non-use aliases (getContext, getKeyDownList). BREAKING(@tanstack/devtools-ui): exported useTheme is renamed to createTheme. * fix(devtools): apply create* rename to tests and docs merged from main #472 added component tests (tabs.test.tsx, settings-tab.test.tsx) using the old useDevtoolsState/useDevtoolsSettings names, and the devtools-plugin-panel skill docs referenced the renamed devtools-ui export useTheme. Update them to the create* names.
by Alem Tuzlak
Failed
feat/event-client-production-stripping
afd8f8e8 Merge 67ed337299cb32a97820df6c6bf097b8e53cbba3 into ea3c6749b07f4328f1c9cb352c05135aa773a22f
by Alem Tuzlak
Succeeded
main
ea3c6749 fix(devtools): rename Solid use* primitives to create* for React Compiler compat (#477) * fix(devtools): rename Solid use* primitives to create* for React Compiler compat The devtools packages are Solid but used React-style naming (useStyles, useTheme, useDevtoolsState, ...) for their custom primitives. When an app enables React Compiler, it matches the use* convention and transforms this Solid code as if it were React, breaking the panel. Rename every custom Solid primitive in @tanstack/devtools, devtools-ui, and devtools-a11y from use* to create*, and import Solid's useContext and @solid-primitives' useKeyDownList under non-use aliases (getContext, getKeyDownList). BREAKING(@tanstack/devtools-ui): exported useTheme is renamed to createTheme. * fix(devtools): apply create* rename to tests and docs merged from main #472 added component tests (tabs.test.tsx, settings-tab.test.tsx) using the old useDevtoolsState/useDevtoolsSettings names, and the devtools-plugin-panel skill docs referenced the renamed devtools-ui export useTheme. Update them to the create* names.
by Alem Tuzlak
Succeeded
fix/devtools-solid-hook-naming
7c8f27f1 fix(devtools): apply create* rename to tests and docs merged from main #472 added component tests (tabs.test.tsx, settings-tab.test.tsx) using the old useDevtoolsState/useDevtoolsSettings names, and the devtools-plugin-panel skill docs referenced the renamed devtools-ui export useTheme. Update them to the create* names.
by Alem Tuzlak
Failed
fix/devtools-solid-hook-naming
7c8f27f1 fix(devtools): apply create* rename to tests and docs merged from main #472 added component tests (tabs.test.tsx, settings-tab.test.tsx) using the old useDevtoolsState/useDevtoolsSettings names, and the devtools-plugin-panel skill docs referenced the renamed devtools-ui export useTheme. Update them to the create* names.
by Alem Tuzlak
Failed
fix/devtools-solid-hook-naming
fd20fa28 Merge 0022e02bd534e85b09a30d1afcad0a42cef2316e into 7114ecd285d9df776fb63595b82cf979adafd51c
by Alem Tuzlak
Succeeded
main
7114ecd2 test: e2e suite (8 apps + server↔client probe) + unit/component coverage (#472) * test(e2e): scaffold Playwright harness, helper package, react-vite app, shell test-ids * test(e2e): full react-vite shell behavior suite + event-probe * ci(e2e): build packages before running the Playwright suite on every PR * test(e2e): react-start runtime app + server probe * test(e2e): extend event-probe with server-ping emitter + receiver * test(e2e): promote react-start to real server->client via #384 runtime bridge; lock e2e deps * test(e2e): react-nitro runtime app + server probe * test(e2e): cloudflare/workerd runtime app * test(e2e): solid adapter smoke * test(e2e): vue adapter smoke * test(e2e): preact adapter smoke * test(e2e): angular adapter smoke * ci(e2e): run all runtime + adapter e2e apps on every PR; lock e2e deps * test(unit): fill pure-function coverage gaps in devtools + devtools-vite * test(component): Solid shell render + reactivity tests * test(component): React adapter portal wiring test * chore(e2e): formatting and lint fixes * fix(devtools-ui): Checkbox reflects controlled `checked` prop updates * chore(knip): declare doc-script entrypoints and ignore generated intent bin stubs * ci: apply automated fixes * ci(e2e): pin actions to commit SHAs (org policy + zizmor) * test(e2e): make server->client probe deterministic (re-emit until delivered) * ci(e2e): run e2e projects serially — parallel dev servers collide on the shared devtools bus port --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Alem Tuzlak
Failed
main
7114ecd2 test: e2e suite (8 apps + server↔client probe) + unit/component coverage (#472) * test(e2e): scaffold Playwright harness, helper package, react-vite app, shell test-ids * test(e2e): full react-vite shell behavior suite + event-probe * ci(e2e): build packages before running the Playwright suite on every PR * test(e2e): react-start runtime app + server probe * test(e2e): extend event-probe with server-ping emitter + receiver * test(e2e): promote react-start to real server->client via #384 runtime bridge; lock e2e deps * test(e2e): react-nitro runtime app + server probe * test(e2e): cloudflare/workerd runtime app * test(e2e): solid adapter smoke * test(e2e): vue adapter smoke * test(e2e): preact adapter smoke * test(e2e): angular adapter smoke * ci(e2e): run all runtime + adapter e2e apps on every PR; lock e2e deps * test(unit): fill pure-function coverage gaps in devtools + devtools-vite * test(component): Solid shell render + reactivity tests * test(component): React adapter portal wiring test * chore(e2e): formatting and lint fixes * fix(devtools-ui): Checkbox reflects controlled `checked` prop updates * chore(knip): declare doc-script entrypoints and ignore generated intent bin stubs * ci: apply automated fixes * ci(e2e): pin actions to commit SHAs (org policy + zizmor) * test(e2e): make server->client probe deterministic (re-emit until delivered) * ci(e2e): run e2e projects serially — parallel dev servers collide on the shared devtools bus port --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Alem Tuzlak
Succeeded
main
b1c1b20f fix(examples): align @tanstack/devtools-a11y version to fix sherif CI (#474) fix(examples): align @tanstack/devtools-a11y to ^0.1.5 across examples The Version Packages release bumped the react a11y example to ^0.1.5 but left the angular example at ^0.1.4, tripping sherif's multiple-dependency-versions check and failing CI on main.
by Alem Tuzlak