@triggery/devtools-redux
Middleware that streams Triggery runtime events into the Redux DevTools browser extension — no Redux required. Every fire, skip, action-start, action-end, error, and cascade event shows up as an action in the DevTools panel, with a growing run history as “state”.
Install
Section titled “Install”pnpm add -D @triggery/core @triggery/devtools-redux npm install --save-dev @triggery/core @triggery/devtools-redux yarn add --save-dev @triggery/core @triggery/devtools-redux bun add -D @triggery/core @triggery/devtools-redux Peer deps: @triggery/core.
What’s inside
Section titled “What’s inside”| Export | Purpose |
|---|---|
reduxDevtoolsMiddleware(options?) | Middleware factory. Pass to createRuntime({ middleware: [...] }). |
DevtoolsReduxOptions | TS type for the options bag. |
Options:
name— Display name in the DevTools “Inspector → Stores” dropdown.historyLimit— How many runs to keep as virtual “state” (default 100).
Quick example
Section titled “Quick example”import { createRuntime } from '@triggery/core';
import { reduxDevtoolsMiddleware } from '@triggery/devtools-redux';
const runtime = createRuntime({
middleware: import.meta.env.DEV
? [reduxDevtoolsMiddleware({ name: 'My App', historyLimit: 200 })]
: [],
});If the Redux DevTools extension isn’t installed (production builds, Node, browsers without the extension), the middleware degrades to a quiet no-op.
Related packages
Section titled “Related packages” @triggery/core The runtime this middleware attaches to.
@triggery/devtools-panel In-app inspector React components.
@triggery/devtools-bridge Page-side bridge for external inspectors.