Small and nice PubSub and event bus library with custom scheduler support.

Generate test suites for checks that already happened at build-time

Assert that a change you expected to happen, happened, with the chai library

React hook to execute callback when a click is happened outside of a component with Shadow DOM support

Small Kefir utility for signifying an event has happened

Track execution paths and outcomes to form an explanation for understanding what happened

Argus decision-to-reality MCP — preserve a user-adopted prediction, its return condition, and what actually happened without scoring the person.

Open a terminal. Write one page. Publish it. Learn what happened.

Know exactly why and how a bug happened. Get reports with screenshots, live action replays and all of the important metadata every time.

pharos — CLI for Mastra's company memory. Ask what happened, who owns what, and what's unresolved.

React component to track clicks that happened outside of it.

Time-aware memory system that understands when things happened, not just what happened

* in pad title when an edit event has happened that you might not have seen

Used to give the user feedback instead of results. For example, error happened, results not found, no results yet.

Simple abstractions for communicating that something happened

thought-frame-moving-happened

Mission control for Claude Code — a status line that tells you what to do, not just what happened.

similar-usual-magnet-happened

Simple unit testing runner that will travel through your files letting you know what happened. Simple, fast and with TypeScript definitions included!

JavaScript SDK for Threadify - Execute business process graphs with context—track what happened, validate every step, and trigger context-aware actions