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

@zudojs/docs

v1.1.0

Published

Documentation infrastructure with structured document model, registry, validation, navigation, and generation.

Downloads

108

Readme

@zudojs/docs

Documentation infrastructure with structured document model, registry, validation, navigation, frontmatter parsing, and markdown/JSON generation.

Documentation: zudojs.oyinlola.site/docs/packages-docs · For AI agents: Markdown version, llms.txt

Installation

npm install @zudojs/docs

Quick Start

import {
  createDocumentRegistry,
  createMarkdownDocument,
  validateAll,
  generateIndex,
} from "@zudojs/docs";

const registry = createDocumentRegistry();

registry.register(
  createMarkdownDocument(
    "getting-started",
    "Getting Started",
    "# Getting Started\n\nWelcome to Zudojs...",
    { category: "introduction", tags: ["intro"] },
  ),
);

// Or build the document object yourself
registry.register({
  id: "guides.http.routing",
  title: "HTTP Routing",
  content: { type: "markdown", value: "# Routing\n\n..." },
});

const result = validateAll(registry.getAll());
if (!result.valid) {
  console.error(result.issues);
}

const index = generateIndex(registry.getAll()); // SERVER-only docs excluded

Features

  • Document model with frontmatter (parseFrontmatter / serializeFrontmatter round-trip safely; tags always parses to a string array, and the body keeps its indentation)
  • Document registry and discovery (DuplicateDocumentError on duplicate IDs, deep-frozen copies)
  • Navigation tree helpers (breadcrumbs, siblings, previous/next, cycle-safe walkers)
  • Markdown and JSON generation with escaping for untrusted content: structured text is HTML-escaped and links are limited to http, https, mailto, tel, ftp and ftps (others are written as plain text)
  • Fail-closed visibility filtering: only an unset or exactly "CLIENT" visibility reaches a client index
  • stripMarkdown and link validation run in linear time on untrusted input
  • Document, link and navigation validation with a single valid rule (errors only); javascript: and other non-allow-listed link schemes are UNSAFE_LINK errors in every link form — inline [x](…) (including targets with parentheses or a title), reference definitions [x]: …, raw <a href="…"> and <scheme:…> autolinks
  • BROKEN_LINK and NAVIGATION_ORPHAN_DOCUMENT are warnings by default; pass { brokenLinkSeverity: "error", orphanSeverity: "error" } to validateAll (or brokenLinkSeverity to validateLinks) to fail on dead links or unreachable documents
  • createDocument({ …, strict: true }) rejects an unknown category, status or visibility at creation instead of leaving it to validateDocument; documents never carry explicit undefined keys
  • getAdjacent(id, nav, { scope: "tree" }) walks previous/next across section boundaries in reading order (the default stays within one level)
  • Documentation error classes re-exported from @zudojs/errors

Use Cases

  • API documentation
  • User guides
  • Knowledge bases
  • Documentation sites