Loading workspace insights... Statistics interval
7 days30 daysLatest CI Pipeline Executions
644bcb3e feat: add @tanstack/intent agent skills (#377)
* feat: add @tanstack/intent agent skills for all packages
Scaffold agent-readable SKILL.md files via @tanstack/intent for AI coding
agents (Claude Code, Cursor, Copilot, etc.) to generate better code when
working with TanStack Devtools.
Skills added (9 total across 4 packages):
- devtools: app-setup, plugin-panel, production, marketplace
- event-bus-client: event-client, instrumentation, bidirectional
- devtools-vite: vite-plugin
- devtools-utils: framework-adapters (React, Vue, Solid, Preact)
Also includes:
- CI workflows for skill validation, staleness checks, and intent notifications
- Domain map, skill spec, and skill tree artifacts
- Intent CLI bin shim and package.json wiring
- README note for AI agent users
* ci: apply automated fixes
* ci: apply automated fixes (attempt 2/3)
* chore: add changeset for intent skills
* ci: apply automated fixes
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com> 3dd09a1e feat: add @tanstack/intent agent skills for all packages
Scaffold agent-readable SKILL.md files via @tanstack/intent for AI coding
agents (Claude Code, Cursor, Copilot, etc.) to generate better code when
working with TanStack Devtools.
Skills added (9 total across 4 packages):
- devtools: app-setup, plugin-panel, production, marketplace
- event-bus-client: event-client, instrumentation, bidirectional
- devtools-vite: vite-plugin
- devtools-utils: framework-adapters (React, Vue, Solid, Preact)
Also includes:
- CI workflows for skill validation, staleness checks, and intent notifications
- Domain map, skill spec, and skill tree artifacts
- Intent CLI bin shim and package.json wiring
- README note for AI agent users 024ea7d6 fix(devtools): prevent solid-js from leaking into server bundles (#367)
* 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> 32828704 docs: comprehensive documentation overhaul (#363)
* docs: add documentation redesign design document
Comprehensive plan for restructuring TanStack Devtools documentation
with layered architecture approach: Getting Started, Concepts, Guides,
API Reference, and Examples sections. Adds 11 new pages including
architecture overview, event system deep-dive, Vue framework support,
and plugin building guides.
* docs: add documentation implementation plan
18-task plan covering: navigation restructure, 4 new Concepts pages
(architecture, event system, plugin lifecycle, source inspector),
3 new Guides (custom plugins, devtools-utils, bidirectional comms),
Vue framework support, Solid custom plugins, and updates to existing
pages including overview, quick-start, installation, and React adapter.
* docs: restructure navigation with Concepts and Guides sections, add Vue
* docs: expand overview with package map and architecture diagram
* docs: add all framework examples to quick start
* docs: add Vue and Preact installation instructions
* docs: add architecture overview page
* docs: add event system concepts page
* docs: add plugin lifecycle concepts page
* docs: add source inspector concepts page
* docs: add framework-agnostic custom plugin building guide
* docs: add devtools-utils guide for plugin factory helpers
* docs: add bidirectional communication guide
* docs: add Vue basic setup and adapter pages
* docs: add Vue and Solid custom plugins guides
* docs: replace TODO in React adapter with actual content
* docs: expand Vite plugin features documentation
* docs: fix event map key convention, typos, and internal link extensions
- Event map keys should be suffix-only (e.g., 'state-update'), not
prefixed with pluginId. EventClient prepends pluginId automatically.
Fixed across all custom plugin guides and concept pages.
- Fix enabled:false docs in event-system.md (emit is a no-op, not
internal dispatch)
- Fix double "the the" typo in installation.md
- Remove .md extensions from internal doc links for consistency
- Fix event map key in configuration.md example
* docs: remove internal plan files
* docs: replace ASCII diagrams with mermaid in architecture overview
* docs: add mermaid diagrams across all documentation pages
- overview.md: architecture layer diagram
- event-system.md: connection lifecycle state diagram
- plugin-lifecycle.md: mount sequence flowchart + portal pattern diagram
- source-inspector.md: inspection flow diagram
- building-custom-plugins.md: plugin architecture overview
- bidirectional-communication.md: two-way flow + time travel sequence diagram
- vite-plugin.md: sub-plugin overview diagram 18135164 docs: comprehensive documentation overhaul (#363)
* docs: add documentation redesign design document
Comprehensive plan for restructuring TanStack Devtools documentation
with layered architecture approach: Getting Started, Concepts, Guides,
API Reference, and Examples sections. Adds 11 new pages including
architecture overview, event system deep-dive, Vue framework support,
and plugin building guides.
* docs: add documentation implementation plan
18-task plan covering: navigation restructure, 4 new Concepts pages
(architecture, event system, plugin lifecycle, source inspector),
3 new Guides (custom plugins, devtools-utils, bidirectional comms),
Vue framework support, Solid custom plugins, and updates to existing
pages including overview, quick-start, installation, and React adapter.
* docs: restructure navigation with Concepts and Guides sections, add Vue
* docs: expand overview with package map and architecture diagram
* docs: add all framework examples to quick start
* docs: add Vue and Preact installation instructions
* docs: add architecture overview page
* docs: add event system concepts page
* docs: add plugin lifecycle concepts page
* docs: add source inspector concepts page
* docs: add framework-agnostic custom plugin building guide
* docs: add devtools-utils guide for plugin factory helpers
* docs: add bidirectional communication guide
* docs: add Vue basic setup and adapter pages
* docs: add Vue and Solid custom plugins guides
* docs: replace TODO in React adapter with actual content
* docs: expand Vite plugin features documentation
* docs: fix event map key convention, typos, and internal link extensions
- Event map keys should be suffix-only (e.g., 'state-update'), not
prefixed with pluginId. EventClient prepends pluginId automatically.
Fixed across all custom plugin guides and concept pages.
- Fix enabled:false docs in event-system.md (emit is a no-op, not
internal dispatch)
- Fix double "the the" typo in installation.md
- Remove .md extensions from internal doc links for consistency
- Fix event map key in configuration.md example
* docs: remove internal plan files
* docs: replace ASCII diagrams with mermaid in architecture overview
* docs: add mermaid diagrams across all documentation pages
- overview.md: architecture layer diagram
- event-system.md: connection lifecycle state diagram
- plugin-lifecycle.md: mount sequence flowchart + portal pattern diagram
- source-inspector.md: inspection flow diagram
- building-custom-plugins.md: plugin architecture overview
- bidirectional-communication.md: two-way flow + time travel sequence diagram
- vite-plugin.md: sub-plugin overview diagram