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

@abraca/schema

v2.10.0

Published

One declaration of doc-types — generates TypeScript, JSON Schema, Rust, MCP tool, and Markdown reference output.

Readme

@abraca/schema

The canonical page-type schema spec for Abracadabra. One Zod declaration per doc-type generates TypeScript, a JSON-Schema bundle, Rust, Swift, and Markdown — so every language validates the same shapes. Zero runtime dependencies.

Documentation

Full, code-derived documentation lives in docs/ — the registry model, the universal meta object, all 16 page types, the query DSL, CRDT markers, the plugin manifest validator, and the codegen pipeline. It is the source of truth (more authoritative than any prose page-type guide).

At a glance

import { defineSchema, Kanban, Doc } from "@abraca/schema";
const schema = defineSchema({ types: [Kanban, Doc] });
schema.validateMeta("kanban", meta);   // {ok:true} for unknown types (Rule 4)
  • 16 page types — doc, prose, kanban, gallery, table, outline, checklist, graph, timeline, calendar, map, dashboard, chart, sheets, slides, overview.
  • Additive / opt-in — no aggregate schema; compose the subset you need; unknown types are never rejected, known types are closed (additionalProperties:false).
  • query.ts is the wire contract the Rust server's query engine mirrors.

::

The generated JSON-Schema bundle (registry/v1.json) is the real cross-language contract — consumed by the Rust SchemaValidationExtension and MCP tool schemas. Never hand-edit src/generated/**; run pnpm schema:gen (CI verifies). yjs/zod are peer deps.

License

MIT.