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

@holdenmatt/md-bundle

v0.4.0

Published

Markdown bundles: one root text file plus related docs, scripts, and assets.

Downloads

718

Readme

@holdenmatt/md-bundle

A Markdown bundle is one root text file plus related files in the same folder tree, addressed by bundle-relative paths.

The root stays the entry point while supporting Markdown files, scripts, and assets let the bundle grow without becoming one giant document. An Agent Skill is one example: SKILL.md is the root, with references, scripts, and assets beside it. Markdown is conventional, but any text file can be the root.

Install

npm install @holdenmatt/md-bundle

Load a bundle

my-skill/
  SKILL.md
  references/checklist.md
  assets/logo.png
import { getTextFile } from "@holdenmatt/md-bundle";
import { loadBundle } from "@holdenmatt/md-bundle/node";

const bundle = await loadBundle("my-skill/SKILL.md");
const checklist = getTextFile(bundle, "references/checklist.md");

For browser or in-memory code, create the same value without filesystem access:

import { createBundle } from "@holdenmatt/md-bundle";

const bundle = createBundle({
  rootPath: "README.md",
  files: [{ path: "README.md", content: "# Example\n" }],
});

Entry points

  • @holdenmatt/md-bundle: browser-safe bundle model, guards, paths, references, and in-memory construction.
  • @holdenmatt/md-bundle/schema: browser-safe structural validation for bundle formats.
  • @holdenmatt/md-bundle/node: Node filesystem loading and writing.

The core and schema entries do not import Node builtins. A MarkdownBundle is a value; where it comes from is an adapter.

Validate a bundle format

Use the optional @holdenmatt/md-bundle/schema entry point to define rules for root files, supporting files, and nested bundles.

import { bundleSchema } from "@holdenmatt/md-bundle/schema";

const skillSchema = bundleSchema({
  root: { path: "SKILL.md" },
  additionalFiles: "allow",
});

const result = skillSchema.parse(bundle);

See Schema guide for typed parsers, file rules, nested bundles, findings, and the complete API.

Documentation