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

pact-cavemod-adapter

v1.0.0

Published

PACT contract and test runner for mod APIs; writes pact-results.json and defines pactStatus for mod index

Readme

pact-cavemod-adapter

PACT contract and test runner for mod APIs. Declares the Mod Index API contract (consumer: ModApiConsumer, provider: ModIndexProvider), and writes pact-results.json after running consumer Pact tests so build/CI can record status as "good" or "fail" in the mod index.

Contract

  • Consumer: ModApiConsumer (e.g. node-mod-editor mod-api-client)
  • Provider: ModIndexProvider (e.g. kotlin-mod-index)
  • Endpoints: GET /api/mods, GET /api/mods/:modId

Mod index contract extension

A mod entry in the index may include:

  • pactStatus (optional): "good" | "fail" | "unknown" — set when PACT consumer tests are run and verified in build/CI.
  • pactVerifiedAt (optional): ISO timestamp of last PACT verification.

The mod index (e.g. kotlin-mod-index) may read pact-results.json or receive status via API and include these fields in GET /api/mods and GET /api/mods/:id responses.

Writing results

After running consumer Pact tests (e.g. npm run test:pact in node-mod-editor):

npx pact-cavemod-write-results pass
# or
npx pact-cavemod-write-results fail

Or programmatically:

import { writePactResults } from 'pact-cavemod-adapter';
writePactResults({ status: 'pass', outputPath: 'pact-results.json' });

Output format: { "consumer": "ModApiConsumer", "provider": "ModIndexProvider", "status": "pass"|"fail", "timestamp": "..." }.

Build and CI

  • Mod build: Run test:pact then pact-cavemod-write-results <pass|fail> so pact-results.json is produced.
  • CI: Run mod build (including pact step); optionally run provider verification and publish pact status to the mod index.

Monorepo usage (log-view-machine)

The mod workspace (log-view-machine/mod) depends on this package via devDependencies: { "pact-cavemod-adapter": "file:../packages/pact-cavemod-adapter" }. From repo root, install mod’s deps then run pact build:

cd mod && npm install && npm run build:pact

From repo root (with mod in workspaces): npm run build:mod:pact or npm run build:pact --workspace=mod. The build:pact script runs node-mod-editor’s test:pact and then writes pact-results.json (pass or fail) into mod/.