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

@odla-ai/docs

v0.1.0

Published

Build-time docs engine for themed human documentation sites and in-app manifests, built on @odla-ai/blog's renderer and the @odla-ai/ui design system.

Downloads

564

Readme

@odla-ai/docs

⚠️ Early access — pre-1.0. Agents work from bounded runbooks; humans approve credentials, production changes, releases, and merges. APIs and exact package availability can change. Review the documented guarantees and limitations; this software is MIT-licensed and provided without warranty.

A build-time docs engine: point it at a directory of markdown and get one manifest that supports two hosts from a single source —

  • a themed human docs site rendered as static HTML, and
  • a serializable content manifest rendered inside an application without shipping a Markdown parser.

It is built on @odla-ai/blog's markdown renderer (marked + build-time highlight.js — no client JS) and the @odla-ai/ui design system (one --ui-* token contract, five themes). Node-only: never import it from browser or Worker code — it pulls in the markdown highlighter.

Content

A content dir is markdown with YAML frontmatter:

---
title: Quickstart
group: Start          # nav section
order: 10             # sort within group; group order = min(page.order)
slug: quickstart      # defaults to the filename
summary: One-line lede.
audience: [operator, agent]
goldenPath: build     # optional: tags a page into an agent golden path
packageRef: "@odla-ai/db"
---
markdown body, with `> [!WARN]` admonitions and inline ui elements…

API

import { loadDocs, buildManifest, renderSite, emitManifestModule } from "@odla-ai/docs";

const pages = await loadDocs("content");        // DocPage[] (html + metadata)
const manifest = buildManifest(pages);          // { groups, pages }
await renderSite({ contentDir: "content", outDir: "dist/docs", theme: "juniper" });
const tsModule = emitManifestModule(manifest);  // @generated data module for an app
  • loadDocs(dir, { includeDrafts }) — parse + render a content tree.
  • buildManifest(pages) — group/order into the nav shape both hosts consume.
  • renderSite({ contentDir, outDir, theme, basePath }) — static site.
  • renderDocPage(manifest, slug, opts) — one page's HTML.
  • emitManifestModule(manifest) — a committed @generated TS module for in-app use.
  • renderMarkdown, slugify, escapeHtml, extractHeadings, applyAdmonitions.

Tests

npm test (node's test runner). npm run coverage (c8, ≥95%). The test/fixture/content tree is the golden corpus.

The installed README is the package contract; exported source JSDoc and the public page at https://odla.ai/docs/packages/docs provide the rendered reference.