npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@triggery/signals

v0.10.0

Published

Signals adapter for Triggery — read a signal's value from a trigger condition without engaging signal-tracking on the host component

Readme

@triggery/signals

Read a signal from a Triggery condition without engaging signal-tracking on the host component. Compatible with:

Install

pnpm add @triggery/core @triggery/react @triggery/signals
# + the signal library of your choice, e.g.
pnpm add @preact/signals-core

Usage

import { signal } from '@preact/signals-core';
import { createTrigger } from '@triggery/core';
import { useSignalCondition } from '@triggery/signals';

const settings = signal({ sound: true, notifications: true });

const messageTrigger = createTrigger<{
  events: { 'new-message': { text: string } };
  conditions: { settings: { sound: boolean; notifications: boolean } };
  actions: { showToast: { body: string } };
}>({
  id: 'message-received',
  events: ['new-message'],
  required: ['settings'],
  handler({ event, conditions, actions }) {
    if (!conditions.settings.notifications) return;
    actions.showToast?.({ body: event.payload.text });
  },
});

function SettingsBridge() {
  useSignalCondition(messageTrigger, 'settings', settings);
  return null;
}

With a selector:

useSignalCondition(messageTrigger, 'settings', profile, (p) => p.settings);

How it works

Pull-only: the signal is read only when a trigger fires. The adapter prefers peek() (no dependency tracking) and falls back to .value if peek is missing. Either way, no subscriber is registered against the signal, so the host component never re-renders on signal updates.

If a component also needs to render the signal, use useSignal() from @preact/signals-react or the equivalent in your signal library — the two paths are orthogonal.

API

useSignalCondition<V, S, K>(
  trigger: Trigger<S>,
  name: K,
  signal: { peek?(): V; readonly value?: V },
  selector?: (value: V) => ConditionMap<S>[K],
): void

Documentation

Full documentation, recipes and API reference at https://triggeryjs.github.io/packages/signals/.

Related packages

See the full package list in the repo README.

License

MIT © Aleksey Skhomenko