Counter

The same counter scenario as the React recipe, but with Solid’s createSignal. The trigger is exactly the same — it lives in @triggery/core and doesn’t know about either framework.

The trigger

src/triggers/counter.trigger.ts

import { createTrigger } from '@triggery/core';

export const counterTrigger = createTrigger<{
  events:  { increment: void; decrement: void };
  actions: { adjust: number };
}>({
  id: 'counter',
  events: ['increment', 'decrement'],
  handler({ event, actions }) {
    actions.adjust?.(event.name === 'increment' ? 1 : -1);
  },
});

The component

src/Counter.tsx

import { useAction, useEvent } from '@triggery/solid';
import { createSignal } from 'solid-js';
import { counterTrigger } from './triggers/counter.trigger';

export function Counter() {
  const [count, setCount] = createSignal(0);

  const inc = useEvent(counterTrigger, 'increment');
  const dec = useEvent(counterTrigger, 'decrement');

  useAction(counterTrigger, 'adjust', delta => setCount(c => c + delta));

  return (
    <div>
      <button onClick={dec}>−</button>
      <output>{count()}</output>
      <button onClick={inc}>+</button>
    </div>
  );
}

Same shape, native to Solid. No re-rendering of the rest of the tree when the count changes — Solid’s fine-grained reactivity does its thing, Triggery’s bindings just register/unregister via onCleanup.

Related

React version The exact same trigger, React hooks.

Vue version Composition API.

Notification pipeline (Solid) The full multi-component scenario.

@triggery/solid package Hook reference.