@tanstack/vue-devtools@0.2.22

Patch Changes

• Updated dependencies [ea3c674]:
  • @tanstack/devtools@0.12.5

@tanstack/svelte-devtools@0.1.1

Patch Changes

• Updated dependencies [ea3c674]:
  • @tanstack/devtools@0.12.5

@tanstack/solid-devtools@0.8.8

Patch Changes

• Updated dependencies [ea3c674]:
  • @tanstack/devtools@0.12.5

@tanstack/react-devtools@0.10.8

Patch Changes

• Updated dependencies [ea3c674]:
  • @tanstack/devtools@0.12.5

@tanstack/preact-devtools@0.10.8

Patch Changes

• Updated dependencies [ea3c674]:
  • @tanstack/devtools@0.12.5

@tanstack/devtools@0.12.5

Patch Changes

• #477 ea3c674 - fix: rename Solid use* primitives to create* so React Compiler doesn't transform them

  The devtools packages are written in Solid but used React-style naming (useStyles, useTheme, useDevtoolsState, …) for their custom primitives. When an app enables React Compiler, the compiler matches the use* naming convention and transforms/optimizes this Solid code as if it were React, breaking the panel (it is Solid JSX, not React).

  All custom Solid primitives in @tanstack/devtools, @tanstack/devtools-ui, and @tanstack/devtools-a11y are renamed from use* to create*, and Solid's own useContext / @solid-primitives useKeyDownList are imported under non-use aliases (getContext, getKeyDownList).

  Breaking for @tanstack/devtools-ui: the exported useTheme is renamed to createTheme.

• Updated dependencies [7114ecd, ea3c674]:

  • @tanstack/devtools-ui@0.6.0
  • @tanstack/devtools-client@0.0.8

@tanstack/devtools-vite@0.8.1

Patch Changes

• Updated dependencies []:
  • @tanstack/devtools-client@0.0.8

@tanstack/devtools-ui@0.6.0

Minor Changes

• #477 ea3c674 - fix: rename Solid use* primitives to create* so React Compiler doesn't transform them

  The devtools packages are written in Solid but used React-style naming (useStyles, useTheme, useDevtoolsState, …) for their custom primitives. When an app enables React Compiler, the compiler matches the use* naming convention and transforms/optimizes this Solid code as if it were React, breaking the panel (it is Solid JSX, not React).

  All custom Solid primitives in @tanstack/devtools, @tanstack/devtools-ui, and @tanstack/devtools-a11y are renamed from use* to create*, and Solid's own useContext / @solid-primitives useKeyDownList are imported under non-use aliases (getContext, getKeyDownList).

  Breaking for @tanstack/devtools-ui: the exported useTheme is renamed to createTheme.

Patch Changes

• #472 7114ecd - Fix Checkbox ignoring controlled checked prop updates. It previously read checked into internal state only once at mount, so it never reflected later prop changes when used as a controlled input (e.g. the devtools settings panel). It now reflects the checked prop whenever it is provided and falls back to internal state only when uncontrolled.

@tanstack/devtools-event-client@0.5.0

Minor Changes

• #471 b1ac893 - The root export of @tanstack/devtools-event-client now resolves to a no-op
  outside development (process.env.NODE_ENV !== 'development'), so the real
  EventClient is tree-shaken out of production bundles by default.

  If you want devtools events to keep working in production, import the real
  client from the new @tanstack/devtools-event-client/production subpath, which
  always ships the real implementation. The public API is identical between the
  two imports.

@tanstack/devtools-client@0.0.8

Patch Changes

• Updated dependencies [b1ac893]:
  • @tanstack/devtools-event-client@0.5.0