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

@mmmnt/feat-adapter-kit

v0.1.6

Published

Conformance suites for Feat adapter authors: prove your adapter honors the capture-window and invoke contracts

Readme

@mmmnt/feat-adapter-kit

Executable conformance suites for Feat adapter authors. Drop one call into your vitest suite and the harness-facing contract is asserted for you — capture-window discipline, record shape, reset semantics, optional-method behavior. Feature's own first-party adapters run these same suites.

Service adapters

import { serviceAdapterContract } from "@mmmnt/feat-adapter-kit";
import { createAdapter } from "../src/index.js";

serviceAdapterContract("my-adapter", {
  factory: () => createAdapter({ options: { /* ... */ } }),
  act: async () => { /* cause one observable effect */ },
  seedRecords: [{ type: "Row", values: { id: 1 } }],   // only if you support seeding
  deliverSample: { event: "X", payload: {} },          // only if event-capable
});

Asserted: empty windows capture nothing; effects inside the window are captured with the { type, payload } record shape; effects before the window are not; reset() is repeatable and clears window state; read() returns records or null; seeded records never leak into capture; unsupported seed() rejects with a clear configuration error; delivered stimuli are excluded from capture.

Response adapters

import { responseAdapterContract } from "@mmmnt/feat-adapter-kit";

responseAdapterContract("my-adapter", {
  factory: () => createAdapter({ commands: { Ping: { /* route */ } } }),
  command: "Ping",
  payload: { n: 1 },
  expectStatus: "OK",
});

Asserted: invoke() returns the { status, body } shape; unrouted commands reject with a configuration error.

vitest is a peer dependency. Part of Feature — adapter contract reference: https://github.com/mmmnt/feature/wiki/Architecture

MIT