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

@sprig-and-prose/tutorial

v0.2.0

Published

CLI to serve the tutorial UI for a workspace of markdown tutorials and docs

Readme

@sprig-and-prose/tutorial

CLI to run a local tutorial UI for a workspace of markdown tutorials and docs.

How to run

tutorial ui [path?]
  • path — Workspace directory (default: current directory).
  • Options:
    • --port <number> — Port (default: 3627).
    • --no-open — Do not open the browser.
    • --config <path> — Path to tutorial.config.json.
    • -h, --help — Show help.

Example:

tutorial ui
tutorial ui ./my-tutorials --port 4000 --no-open

Workspace structure

  • Tutorials — Any .md file at the workspace root, or any .md file inside a direct subdirectory of the root. Each file should have exactly one # (H1) title and one or more ## (H2) headings; the UI splits on H2 into pages with next/previous navigation.
  • Docs — Optional docs/ directory; each .md file is listed under Docs and rendered as a single page (no H2 splitting).
  • Assets — Optional assets/ directory; files are served at /workspace-assets/<path>. In markdown, reference images with /workspace-assets/image.png.

Only these directories are ignored when scanning for tutorials: the configured docsDir and assetsDir, plus .git, node_modules, and dist. No other heuristics.

Optional config

Create tutorial.config.json in the workspace root:

{
  "title": "My Tutorials",
  "assetsDir": "static",
  "docsDir": "pages"
}
  • title — Optional string; shown in the UI.
  • assetsDir — Optional path (relative to workspace) for static assets; default is assets if that folder exists.
  • docsDir — Optional path for doc markdown; default is docs if that folder exists.

What you get

After running tutorial ui:

  • A calm startup line: workspace path, number of tutorials, docs enabled/none, assets enabled/none, and the URL (e.g. http://localhost:3627).
  • The browser opens to that URL (unless you use --no-open).
  • The UI shows a left sidebar listing all tutorials and docs; the main panel shows the selected tutorial (H2-split pages with next/prev) or doc (single page). Images under assets load from /workspace-assets/.

No hot reload; this is a static lens over your workspace.