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 🙏

© 2025 – Pkg Stats / Ryan Hefner

jsdoc-example-runner

v1.0.5

Published

Run embedded code examples from JSDoc comments as real tests.

Readme

jsdoc-example-runner

Run embedded code examples from JSDoc comments as real tests.

jsdoc-example-runner scans a source file, extracts code blocks inside JSDoc comments, and executes them in the same module context as the file they came from. This makes your documentation examples executable and ensures they always stay in sync with your actual code.

✨ Features

  • ▶️ Executes ts or js code blocks from /*_ ... _/ JSDoc comments

  • 🔍 Automatically extracts fenced code examples:

/**
 * ```ts
 * console.log(sum(1, 2));
 * ```
 */
export function sum(a: number, b: number): number {
  return a + b;
}
  • 📄 Runs examples by appending them to the original file's module scope

  • 🧪 Ensure the examples are updated with the code

  • 🛠 Supports TypeScript or JavaScript files

📘 Example Usage

Suppose you have a simple utility with JSDoc-embedded examples:

sum.ts

/**
 * ```ts
 * expect(sum(1, 2)).toBe(3);
 * expect(sum(5, -3)).toBe(2);
 * ```
 */
export function sum(a: number, b: number): number {
  return a + b;
}

Then create a small script to run the documentation examples:

sum.test.ts

import path from "path";
import { runExamplesInFile } from "jsdoc-example-runner";
import { test } from "bun:test";

test("Simple sum", async () => {
  await runExamplesInFile(path.resolve(import.meta.path, "path/to/sum.ts"));
});

⚠️ Notes & Limitations

  • Examples must be fenced inside JSDoc comments using backticks (```ts or ```js).

  • Code is executed as-is using whatever runtime runModuleString provides.

  • Examples run sequentially, in the order they appear.

  • Return values are not captured — use assertions for verification.