Adapters

Adapters bridge your existing state manager or event source into Triggery without subscribing host components to updates. Each one is a thin hook that registers a condition or an event with the runtime.

State adapters

Package	Hook	Purpose
@triggery/zustand	useZustandCondition(trigger, name, store, selector)	Expose a Zustand slice as a condition.
@triggery/redux	useReduxCondition(trigger, name, store, selector)	Expose a Redux selector as a condition.
@triggery/jotai	useJotaiCondition(trigger, name, store, atom, selector?)	Read a Jotai atom lazily.
@triggery/mobx	useMobxCondition(trigger, name, () => observable)	No dependency tracking on the host component.
@triggery/reatom	useReatomCondition(trigger, name, atom, selector?)	Reatom v3 (v1000+) atoms.
@triggery/signals	useSignalCondition(trigger, name, signal, selector?)	@preact/signals-core, alien-signals, any peek() / .value signal.
@triggery/query	useQueryCondition(trigger, name, queryClient, queryKey, selector?)	TanStack Query cache.

Event-source adapters

Pipe events from outside the React/Solid/Vue render tree into triggers.

Package	Hook	Purpose
@triggery/dom	useDomEvent, useResizeObserver, useIntersectionObserver	Wire DOM events and observers to a useEvent emitter.
@triggery/socket	useSocketIoEvent, useWebSocketEvent	Wire socket.io-client or native WebSocket frames.

Tip

Adapters are intentionally tiny — most are ~30 lines. If you want to support a state manager not on this list, copying one of the existing adapters (e.g. @triggery/zustand) is the fastest way to do it. PRs welcome.

Integrations Build tools, ESLint, codemod, CLI, devtools.

Showcase Projects shipping Triggery in production.

Conditions guide The role adapters play in a scenario.