Overview - Devtools

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
main
10f28d85 docs: add README header banners to the framework adapter packages (#491)
by Alem Tuzlak
Succeeded
readme-header-adapters
7214611d Merge 06017fb365d830bb60eb764f5754f66b5c7ff1e8 into 5267bf582231186cf91ed822842f2c95fb2c019b
by Alem Tuzlak
Succeeded
main
5267bf58 docs: use the dynamic README header endpoint (#490)
by Alem Tuzlak
Succeeded
readme-header-endpoint
0f7c4f96 docs: use the dynamic README header endpoint
by Alem Tuzlak
Succeeded
renovate/tanstack-config-digest
b73dd6f5 Merge b823a6a18e5117bee63927a0d23be146ef6fe7ed into 06006350d61a3d7bc02a38ce231c9811330b841d
by renovate[bot]
Succeeded
main
06006350 ci: Version Packages (#487) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Succeeded
main
f4c35d29 fix(devtools-vite): preserve valid syntax when removing devtools JSX (#480) * fix(devtools-vite): preserve valid syntax when removing devtools JSX * add changeset * ci: apply automated fixes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Vedant Pahune
Succeeded
fix/remove-devtools
4f731ff8 Merge 09ca25b962123b141075ea4ace0c82bf3e0c0bce into f9553f5a88a9b883ff6f48afeea0dbb4cadbbd8d
by Vedant Pahune
Succeeded
fix/remove-devtools
de9261f2 Merge c78d6d475805e7c0b0a1105eb7411229431ab8ba into f9553f5a88a9b883ff6f48afeea0dbb4cadbbd8d
by Vedant Pahune
Succeeded
main
f9553f5a ci: Version Packages (#486) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Failed
main
f9553f5a ci: Version Packages (#486) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
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
9ff7d13f ci: apply automated fixes
by autofix-ci...
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
6525426a ci: apply automated fixes
by autofix-ci...
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