tanstack-devtools

Unify TanStack Query and Router debugging into a single devtools panel.

Updated Jul 2, 2025
One-click install
npx skills add https://github.com/janpeterd/dotfiles --skill tanstack-devtools-janpeterd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tanstack-devtools
Source: https://github.com/janpeterd/dotfiles/tree/main/dot_agents/skills/tanstack-devtools
Command: npx skills add https://github.com/janpeterd/dotfiles --skill tanstack-devtools-janpeterd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TanStack apps often require switching between multiple, framework-specific debugging tools to inspect queries, routes, and AI workflow behavior.

Core Features & Use Cases

  • Unified Devtools Panel: Consolidates TanStack Query, Router, and other library debugging into a single interface.
  • Plugin Architecture: Extends the panel with custom plugins to render additional inspectors and panels.
  • Real-Time State Inspection: Enables live monitoring of state changes and deeper inspection during development.

Use case: When diagnosing a complex frontend issue, configure the Query and Router plugins together (and optionally AI) so you can correlate cache activity, navigation state, and AI tool calls without jumping between separate devtools panes.

Quick Start

Install the required devtools package, then wrap your app with QueryClientProvider and render TanStackDevtools in your root component.

Frequently Asked Questions about tanstack-devtools

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug TanStack Query and Router state in one panel?

You can debug TanStack Query and Router state in one panel by installing the devtools core package, wrapping your app with QueryClientProvider, and rendering TanStackDevtools in your root component to inspect real-time state updates together.

What is the best way to inspect TanStack routing and query behavior simultaneously?

The best way to inspect routing and query behavior simultaneously is using a unified devtools panel that consolidates TanStack library debuggers, allowing you to correlate cache activity and navigation state without switching panes.

Can I extend TanStack devtools with custom debugging plugins?

Yes, you can extend TanStack devtools with custom debugging plugins by leveraging its plugin-driven architecture, which supports rendering custom inspector components with unique IDs alongside the default Query and Router panels.

Does unified TanStack debugging work for AI-enabled workflows?

Unified TanStack debugging works for AI-enabled workflows by applying the devtools panel during development to inspect AI tool calls alongside real-time Query cache updates and Router navigation state changes.

Do I need multiple devtools packages to debug a complex TanStack frontend app?

You do not need multiple separate devtools packages; the unified devtools approach requires a TanStack devtools core package combined with framework-specific packages to consolidate Query, Router, and custom plugin debugging into a single interface.

Why does diagnosing frontend issues require switching between TanStack devtools?

Diagnosing issues requires switching between devtools because TanStack apps traditionally use separate, framework-specific debugging tools to inspect queries and routes, a problem solved by centralizing state inspection into a unified panel.