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/example.harness-lab

v3.7.12

Published

Focused harness example for ContractSpec scenarios, suites, orchestration, and runtime adapters.

Readme

@contractspec/example.harness-lab

Website: https://contractspec.io

Focused harness example for scenario contracts, suites, orchestration, and real runtime adapters.

What This Demonstrates

  • Contract layer: canonical harness-scenario and harness-suite exports.
  • Orchestration layer: HarnessRunner, HarnessEvaluationRunner, and replay bundle generation.
  • Runtime layer: SandboxedCodeExecutionAdapter, PlaywrightBrowserHarnessAdapter, DefaultHarnessTargetResolver, and InMemoryHarnessArtifactStore.
  • A deterministic local browser fixture that stays offline and exercises the real Playwright lane.
  • src/docs/ contains docblocks and documentation-facing exports.

Running Locally

From packages/examples/harness-lab:

  • bunx playwright install chromium
  • bun run build
  • bun run test
  • bun run typecheck

Usage

Use @contractspec/example.harness-lab as the focused harness reference package. It pairs with @contractspec/example.agent-console, which remains the business-oriented proof example for harness contracts.

Architecture

  • src/docs/ contains docblocks and documentation-facing exports.
  • src/example.ts is the runnable example entrypoint.
  • src/harness-lab.feature.ts defines the feature entrypoint for docs/discovery.
  • src/index.ts is the root public barrel and package entrypoint.
  • src/runtime/ contains the runnable sandbox and browser evaluation helpers plus the local browser fixture.
  • src/scenarios/ contains the focused scenario contracts.
  • src/suite/ contains the dual-mode harness suite contract.

Public Entry Points

  • Export . resolves through ./src/index.ts.
  • Export ./docs resolves through ./src/docs/index.ts.
  • Export ./docs/harness-lab.docblock resolves through ./src/docs/harness-lab.docblock.ts.
  • Export ./example resolves through ./src/example.ts.
  • Export ./harness-lab.feature resolves through ./src/harness-lab.feature.ts.
  • Export ./runtime resolves through ./src/runtime/index.ts.
  • Export ./runtime/runBrowserEvaluation resolves through ./src/runtime/runBrowserEvaluation.ts.
  • Export ./runtime/runSandboxEvaluation resolves through ./src/runtime/runSandboxEvaluation.ts.
  • Export ./scenarios resolves through ./src/scenarios/index.ts.
  • Export ./scenarios/harnessLabBrowser.scenario resolves through ./src/scenarios/harnessLabBrowser.scenario.ts.
  • Export ./scenarios/harnessLabSandbox.scenario resolves through ./src/scenarios/harnessLabSandbox.scenario.ts.
  • Export ./suite resolves through ./src/suite/index.ts.
  • The package publishes 12 total export subpaths; keep docs aligned with package.json.

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 prebuild — contractspec-bun-build prebuild

Notes

  • Browser tests use a real local Playwright run against an in-package HTTP fixture. Install Chromium locally before running bun run test.