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

@alert-whatif/core

v0.1.1

Published

Framework-agnostic alert evaluator and scenario library. Pure TypeScript — no React, no Vue, no Grafana SDK. Consumed by @alert-whatif/plugin and @alert-whatif/demo.

Readme

@alert-whatif/core

Framework-agnostic alert evaluator and scenario library for the alert-whatif project.

Pure TypeScript. No React, no Vue, no Grafana SDK. Consumed by:

Both shells import the same evaluation math from this package, so client-side replay in the demo and server-validated what-if in the plugin can never drift.

Status

Scaffolding only. No business logic yet. Real evaluation primitives — counter → rate → reducer → threshold → state machine → notification — land in Step 8 of the build plan, after the product vision, architecture, and MVP scope docs are agreed (Steps 5–7).

Develop

pnpm test           # run tests once
pnpm test:watch     # watch mode
pnpm typecheck      # tsc --noEmit

Test stack

Vitest — TypeScript-native, ESM-first, ~3–5× faster than Jest for pure TS packages with an API that is near-identical to Jest's (describe / it / expect).

@alert-whatif/plugin uses Jest instead because Grafana's plugin template embeds Jest in its protected .config/ directory. The two test runners live side-by-side without conflict; the API surface is so similar that contributors moving between packages do not need to context-switch.

Why a separate package

Because both shells (plugin + demo) need the same math, and because keeping it in a framework-free package is the only way to guarantee no Grafana / React import accidentally creeps in. Every PR touching this package is required to keep it React-free and Grafana-free; the test suite runs in a Node environment with no DOM and no @grafana/* import allowed.

License

MIT