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

@sharpee/transcript-tester

v0.9.106

Published

Transcript-based testing tool for Sharpee interactive fiction

Readme

@sharpee/transcript-tester

Transcript-based integration testing for Sharpee interactive fiction stories. Write tests that read like gameplay transcripts — player commands paired with assertions on text output, semantic events, and world state.

Quick Start

# Published stories: build and test in one step
npx sharpee build --test

# Sharpee development: use the pre-built bundle (~170ms load)
node dist/cli/sharpee.js --test stories/my-story/tests/transcripts/*.transcript

Example

title: Locked Door
story: my-story
description: Verify the brass key unlocks the cellar door

---

> examine door
[OK: contains "locked"]
[EVENT: true, type="if.event.examined"]

> unlock door with brass key
[OK: contains "unlocked"]
[STATE: true, door.isLocked = false]

> open door
[EVENT: true, type="if.event.opened"]

Features

  • Text assertions[OK: contains "..."], [OK: not contains "..."], [OK: matches /regex/]
  • Event assertions — Verify semantic events by type, position, and data
  • State assertions — Check entity properties and inventory after commands
  • Control flowGOAL/END GOAL, IF/END IF, WHILE/END WHILE, DO/UNTIL, RETRY
  • Save/restore — Checkpoint world state for walkthrough chaining
  • Navigation[NAVIGATE TO: "Room"] auto-pathfinds via BFS
  • Test commands$teleport, $take, $kill, $immortal for quick setup

Documentation

For the full guide covering syntax, assertions, directives, CLI flags, and best practices:

Transcript Testing Guide

Architecture decisions:

Package Structure

| File | Purpose | |------|---------| | src/parser.ts | Parses .transcript files into structured test data | | src/runner.ts | Executes transcripts against the game engine | | src/condition-evaluator.ts | Evaluates condition expressions for directives | | src/navigator.ts | BFS pathfinding for NAVIGATE TO | | src/reporter.ts | Formats test results for terminal output | | src/cli.ts | Standalone CLI entry point | | src/fast-cli.ts | Bundle-optimized CLI (used by dist/cli/sharpee.js) | | src/types.ts | TypeScript type definitions for transcripts, assertions, and directives |

API

The package exports its parser and runner for programmatic use:

import { parseTranscript, TranscriptRunner } from '@sharpee/transcript-tester';

const transcript = parseTranscript(fileContents);
const runner = new TranscriptRunner(gameEngine);
const results = await runner.run(transcript);