Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: vitejs/devtools
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.1.23
Choose a base ref
...
head repository: vitejs/devtools
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.1.24
Choose a head ref
  • 4 commits
  • 17 files changed
  • 1 contributor

Commits on May 15, 2026

  1. fix(core): split client/server tsdown builds to keep ws/node out of b… 

    …rowser (#347)
    @antfu
    antfu authored May 15, 2026
    Configuration menu
    Copy the full SHA
    3085997 View commit details
    Browse the repository at this point in the history

  2. chore: update deps

    @antfu
    antfu committed May 15, 2026
    Configuration menu
    Copy the full SHA
    d8efd10 View commit details
    Browse the repository at this point in the history

  3. fix(ci): switch tsdown config-loader from tsx to unrun (#349) 

    * fix(ci): pin tsx to ~4.21.0 to avoid 4.22.0 node: builtin regression

tsx 4.22.0 upgraded its bundled esbuild to 0.28, which broke node:*
builtin resolution in tsx's loader hooks — specifiers like
`node:child_process?tsx-namespace=...` are now read as files and fail
with ENOENT. This breaks `packages/core`'s `tsdown --config-loader=tsx`
build because the config's `build:before`/`build:done` hooks dynamically
import `.ts` files that use Node builtins.

Add tsx to overrides so transitive peer-dep resolutions don't pull
4.22.0 back in via vite/vitepress/tsdown. Drop pin when tsx#756 ships.

Refs: privatenumber/tsx#750

* fix(ci): switch tsdown config-loader from tsx to unrun

The previous tsx pin to ~4.21.0 was a false fix. The bug exists in tsx
4.21.x too — it surfaces on Node 24.15.0 (CI's lts/*) but not 24.12.0.
tsx's loader hook appends `?tsx-namespace=<timestamp>` to specifiers and
Node 24.15.0 then attempts a readFileSync on `node:child_process?...`,
failing with ENOENT.

Switch tsdown's --config-loader from `tsx` to `unrun` in core and the
three example plugins. unrun handles the config and the build:before /
build:done hooks' dynamic `.ts` imports without going through tsx's
loader hook.

Revert the catalog tsx pin and override added in the previous commit
since they no longer carry weight.

* fix(ci): revert devframe to 0.2.2 to unblock typecheck

The 0.2.3 bump from `chore: update deps` (d8efd10) made the build fail
first via the tsx loader bug — once that was unblocked by switching to
the unrun config loader, 86 typecheck errors surfaced. Every `declare
module '@vitejs/devtools-kit'` augmentation in kit/core (registering
RPC server functions, client functions, and shared-state keys) stopped
merging into the re-exported `DevToolsRpc*` interfaces, leaving them as
the empty base from devframe/types.

Pin the catalog and submodule back to 0.2.2 to restore the green state
on commit 3085997. The devframe-side cause needs investigating
upstream; revisit when 0.2.4+ ships.
    @antfu
    antfu authored May 15, 2026
    Configuration menu
    Copy the full SHA
    d1dddbf View commit details
    Browse the repository at this point in the history

  4. chore: release v0.1.24

    @antfu
    antfu committed May 15, 2026
    Configuration menu
    Copy the full SHA
    31c479c View commit details
    Browse the repository at this point in the history
Loading