devtools-event-client

Create a typed event client connecting applications to TanStack Devtools panels.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/cill-i-am/task-tracker --skill devtools-event-client-cill-i-am
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devtools-event-client
Source: https://github.com/cill-i-am/task-tracker/tree/main/.agents/skills/tanstack-devtools-event-client
Command: npx skills add https://github.com/cill-i-am/task-tracker --skill devtools-event-client-cill-i-am

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Typed event emitter/listener that connects application code to TanStack Devtools panels. Framework-agnostic. Works in React, Vue, Solid, Preact, and vanilla JS.

Core Features & Use Cases

  • Define an Event Map and Create a Singleton Client
  • Emit Events
  • Listen to Events
  • Connection Lifecycle and Disabling

Quick Start

Instantiate the singleton client in your app and start emitting events to connect to the TanStack Devtools bus.

Frequently Asked Questions about devtools-event-client

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

FAQPage Schema
How do I create a typed event bus to connect my app to TanStack DevTools panels?

You create a typed event bus by defining an Event Map and instantiating the singleton EventClient. This provides a typed communication layer using emit/on APIs to connect application code directly to TanStack DevTools panels.

Can I use a TanStack DevTools event client across different frameworks like Vue or Solid?

Yes, the event client is framework-agnostic and works across React, Vue, Solid, Preact, and vanilla JS. It provides a singleton pattern for instrumenting application events regardless of the rendering framework used.

How does the event client handle SSR environments and initial connection failures?

The event client implements SSR fallbacks and lazy connection with retries to handle initial connection failures. It also features event queuing, ensuring events emitted before the connection is established are not lost.

How do I emit and listen to events for debugging a TanStack DevTools plugin?

You emit and listen to events by using the client's emit and on APIs with a specified pluginId. This typed layer allows you to send and receive debugging and instrumentation data directly from your application to the devtools panels.

What is the best way to manage the lifecycle of a devtools event bus connection?

The best way to manage the connection lifecycle is through the configurable EventClient singleton. It supports lazy connections, automatic retries, event queuing, and allows you to disable the connection when instrumentation is no longer needed.