Professional debugging tools for signals - inspect, profile, and visualize your reactive state!
enableDevTools()Update the counters below and see how DevTools tracks every change!
SignalForge includes comprehensive development tools for professional debugging:
import { enableDevTools } from 'signalforge/devtools';
// Enable in development only
if (process.env.NODE_ENV === 'development') {
ย ย enableDevTools();
}See how signals and computed values connect. Understand data flow at a glance with interactive dependency graphs.
Track computation times, identify bottlenecks, and optimize your reactive code with detailed profiling data.
Inspect any signal's current value, history, and subscribers. Debug complex state interactions easily.
Step back through signal changes, replay state transitions, and debug issues with full history playback.
import { enableDevTools } from 'signalforge/devtools';
// Enable DevTools (development only)
if (process.env.NODE_ENV === 'development') {
enableDevTools();
}
// Your signals will now be tracked and visible in DevTools
const count = createSignal(0);
const doubled = createComputed(() => count.get() * 2);
// Open Chrome DevTools โ SignalForge panelenableDevTools(config?)Enable DevTools with optional configuration for performance tracking, console logging, and Flipper integration.
listSignals()Get a list of all active signals with their IDs, values, and dependency information.
getSignal(id)Inspect a specific signal by ID to see its current value, subscribers, and dependencies.
getDependencyGraph()Get the complete dependency graph showing how all signals and computed values are connected.
Always wrap enableDevTools() in a development check. DevTools are automatically disabled in production.
When disabled, all DevTools operations become no-ops with no performance impact.
Use the performance profiler to identify slow updates and optimize your reactive code.
Use getDependencyGraph() to visualize and understand complex signal relationships.
Explore other debugging and optimization demos: