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

@dobeerman/avro-docgen

v1.0.1

Published

Generate deterministic Markdown documentation from Apache Avro schema files.

Downloads

453

Readme

avro-docgen

avro-docgen generates deterministic Markdown documentation from Apache Avro .avsc schema files.

The package is published to the npm registry, while repository development uses pnpm only.

Requirements

  • Node.js 24
  • Corepack enabled
  • pnpm managed by the packageManager field

Development

corepack enable
pnpm install --frozen-lockfile
pnpm run ci
pnpm typecheck
pnpm check
pnpm test
pnpm build

Commits and Releases

This repository uses conventional commits, commitlint, Husky, and semantic-release.

Local commits are checked with the repository-local commitlint installation. CI also validates commit messages for pull requests and pushes.

Examples:

feat: add schema reference resolution
fix: render nullable defaults deterministically
chore(release): update release automation

Release-triggering commits:

  • fix: creates a patch release.
  • feat: creates a minor release.
  • commits with BREAKING CHANGE: in the footer create a major release.

Publishing is automated from main through semantic-release. The release workflow runs pnpm run ci, calculates the next version from conventional commits, publishes the package to the npm registry, generates release notes, and creates a GitHub release. npm trusted publishing/OIDC should be configured for the repository before the first real release.

Run the CLI during development:

pnpm dev generate --schema-root test/fixtures/simple-inline/schemas --output tmp/docs

Run a one-off CLI through pnpm:

pnpm dlx @dobeerman/avro-docgen generate

Configuration

Configuration is loaded with cosmiconfig using the avrodoc module name. Supported locations include .avrodocrc, .avrodocrc.json, .avrodocrc.yaml, .avrodocrc.yml, avrodoc.config.json, avrodoc.config.yaml, avrodoc.config.yml, and the avrodoc field in package.json.

{
  "schemaRoots": ["schemas"],
  "schemaPatterns": ["**/*.avsc"],
  "outputDir": "docs/avro",
  "readmeFile": "README.md"
}

Current Scope

The first vertical slice supports config loading, schema scanning, basic named-type parsing, and a minimal generate command that writes a Markdown README for simple schemas. HTML output, Schema Registry integration, template engines, plugin systems, servers, databases, queues, and web UIs are outside v1 scope.