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

@contractspec/module.examples

v4.0.10

Published

Example contract specifications collection

Downloads

2,905

Readme

@contractspec/module.examples

Website: https://contractspec.io

Catalog-first ContractSpec example metadata, with optional runtime helpers for rich example surfaces.

What It Provides

  • Layer: module.
  • Consumers: CLIs, editor bridges, apps, docs, and rich sandbox/template surfaces.
  • Related ContractSpec packages include @contractspec/example.agent-console, @contractspec/example.ai-chat-assistant, @contractspec/example.ai-support-bot, @contractspec/example.analytics-dashboard, @contractspec/example.calendar-google, @contractspec/example.content-generation, ...
  • agent-console is the default autonomous-agent showcase surfaced through /sandbox.
  • data-grid-showcase is the canonical ContractSpec table showcase surfaced through /sandbox?template=data-grid-showcase and /docs/examples/data-grid-showcase.

Installation

npm install @contractspec/module.examples

or

bun add @contractspec/module.examples

Usage

Use the root entrypoint or @contractspec/module.examples/catalog for metadata-only discovery. Use @contractspec/module.examples/runtime only when rendering rich template previews or sandbox runtime surfaces. The catalog also exposes shared preview-surface helpers so apps can show every discoverable example while loading rich UI only for packages that export ./ui.

import { getExample, listExamples } from '@contractspec/module.examples/catalog';
import { ExampleWebPreview, TemplateRuntimeProvider, listTemplates } from '@contractspec/module.examples/runtime';

The catalog contains source metadata for each example. CLI users can fetch a full example only when needed:

contractspec examples download minimal --out-dir ./examples/minimal

Architecture

  • src/builtins.ts is a generated literal catalog and must not statically import @contractspec/example.* packages.
  • src/catalog.ts is the metadata-only public surface.
  • src/index.ts is the root public barrel and package entrypoint.
  • src/registry.test.ts is part of the package's public or composition surface.
  • src/registry.ts is part of the package's public or composition surface.
  • src/runtime is the optional rich runtime surface for consumers that intentionally install example packages.

Public Entry Points

  • Export . resolves through ./src/index.ts and is catalog-only.
  • Export ./catalog resolves through ./src/catalog.ts.
  • Export ./runtime resolves through ./src/runtime/index.ts.

Local Commands

  • bun run dev — contractspec-bun-build dev
  • bun run build — bun run prebuild && bun run build:bundle && bun run build:types
  • bun run test — bun test
  • bun run lint — bun lint:fix
  • bun run lint:check — biome check .
  • bun run lint:fix — biome check --write --unsafe --only=nursery/useSortedClasses . && biome check --write .
  • bun run typecheck — tsc --noEmit
  • bun run publish:pkg — bun publish --tolerate-republish --ignore-scripts --verbose
  • bun run publish:pkg:canary — bun publish:pkg --tag canary
  • bun run clean — rimraf dist .turbo
  • bun run build:bundle — contractspec-bun-build transpile
  • bun run build:types — contractspec-bun-build types
  • bun run generate:registry — bun ../../../scripts/generate-example-registry.ts --write
  • bun run prebuild — bun run generate:registry && contractspec-bun-build prebuild

Recent Updates

  • Replace eslint+prettier by biomejs to optimize speed.
  • Add table capabilities.
  • Stability.
  • Vnext ai-native.

Notes

  • This module is a thin catalog/runtime bridge -- business logic belongs in individual example packages under packages/examples/.
  • Adding a new example requires creating the example package and regenerating the catalog with bun run generate:registry; do not add it as a direct dependency here.
  • Root/catalog imports must remain metadata-only. Rich runtime consumers should import @contractspec/module.examples/runtime and own any required @contractspec/example.* dependencies directly.
  • The meetup-ready autonomous-agent path is the deterministic agent-console sandbox plus its replay proof lane.
  • The shared ContractSpec table stack is demonstrated directly by data-grid-showcase and reused in analytics-dashboard, crm-pipeline, integration-hub, and agent-console.