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

@lovelaces-io/storyteller

v0.2.0

Published

Lightweight TypeScript logging library that treats logs as stories: grouped notes emitted as a single structured event.

Readme

Storyteller

npm license zero deps

Lightweight TypeScript logging library that treats logs as stories — grouped notes emitted as a single structured event.

Zero dependencies. TypeScript-first. One record per story.

Why Storyteller?

Before: 47 scattered console.log lines. Something broke. Good luck figuring out what happened.

[14:30:00] User clicked checkout
[14:30:00] Validating cart...
[14:30:01] Cart valid
[14:30:01] Charging card...
[14:30:03] ERROR: gateway timeout
[14:30:03] Retrying...
[14:30:04] Charge succeeded

After: One story. One record. The whole picture.

{
  "level": "Warning",
  "title": "Payment retry succeeded",
  "durationMs": 4000,
  "notes": [
    { "timestamp": "14:30:00", "note": "User clicked checkout" },
    { "timestamp": "14:30:01", "note": "Cart validated", "what": { "items": 3 } },
    { "timestamp": "14:30:03", "note": "Card declined", "error": { "message": "gateway timeout" } },
    { "timestamp": "14:30:04", "note": "Retry succeeded" }
  ]
}

Install

npm install @lovelaces-io/storyteller

Quick Start

import { Storyteller } from "@lovelaces-io/storyteller";

const story = new Storyteller({
  origin: { who: "checkout-service", where: { app: "web" } },
});

story.note("User submitted payment", { what: { amount: 49.99 } });
story.note("Charging card", { where: "stripe" });
story.tell("Payment completed");

Notes are collected, sorted chronologically, and emitted as one structured event to your audiences.

Two Output Modes

| Mode | What it is | Use it for | |------|-----------|------------| | Story (JSON) | Clean serializable record | DB storage, monitoring, audit logs | | Report (text) | Colorized human-readable output | Console, log files, debugging |

JSON.stringify(event) gives you the story record. formatStory(event) gives you the report.

Three Levels

story.tell("Payment completed");              // all good
story.warn("Payment slow but succeeded");     // heads up
story.oops("Payment failed", new Error());    // something broke

Context on Every Note

story.note("Write failed", {
  who: { id: "user:99" },
  what: { field: "email" },
  where: "primary-db",
  error: new Error("db timeout"),
});

Audiences — Who Hears Your Stories

Stories are delivered to audiences. Console is included by default.

import { dbAudience } from "@lovelaces-io/storyteller";

// Store warn and oops events in your database
story.audience.add(
  dbAudience(async (event) => await db.insert("logs", event))
);

// Target specific audiences
story.oops("Critical failure", error).to("console", "db");

Quick Reference

| Method | Returns | Description | |--------|---------|-------------| | note(text, context?) | this | Add a timestamped note with optional who/what/where/error | | tell(title) | { to } | Tell a success story | | warn(title) | { to } | Tell a cautionary story | | oops(title, error?) | { to } | Tell an error story | | reset() | this | Clear notes without telling a story | | summarize(options?) | FormattedReport | Preview current notes as a formatted report | | audience.add(member) | this | Register an audience | | audience.remove(name) | this | Unregister an audience | | audience.has(name) | boolean | Check if an audience is listening | | audience.names() | string[] | List who's listening |

Shared Instance

import { useStoryteller } from "@lovelaces-io/storyteller";

const story = useStoryteller({ origin: { who: "worker" } });

Docs

License

MIT