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

@openuji/speculator

v0.5.4

Published

AST-first specification processor with schema-central architecture

Readme

@openuji/speculator

AST-first specification parser and indexer with a schema-central architecture.

Speculator is the core engine of the Speculator ecosystem. It transforms specification documents (Markdown or HTML) into a structured AST and semantic indexes. Unlike traditional tools, it does not render output directly—it provides the semantic foundation for renderers, linters, and other processors.

🏗️ Architecture: The 3-Stage Pipeline

Speculator operates on a strict three-stage pipeline to ensure determinism and semantic accuracy:

1. Preprocess (Composition)

Handles configuration loading and spec composition. It resolves includes (both Markdown directives and HTML markers) into a deterministic CompositeSource.

  • Isomorphic IO: Uses FileProvider adapters for Node.js, Web, or Memory environments.
  • Cycle Detection: Prevents infinite include loops with actionable diagnostics.

2. Parse (IR Reconstruction)

Converts the CompositeSource into the Speculator AST. This stage is powered by dedicated parser modules that ensure Markdown and HTML parity.

  • Unified AST: Whether source is ## Heading or <h2>Heading</h2>, the output is a BlockHeading node.
  • Source Tracking: Every node preserves its original sourcePos.file, even across multiple includes.

3. Postprocess (Semantic Enrichment)

A plugin-based pipeline that refines the AST:

  • Transform: Structural normalization.
  • Resolve: Semantic binding (connecting cross-references to definitions).
  • Index: Extracting derived data (definitions, requirements, issues, examples).
  • Compute: Optional generation of TOCs and heading numbering.

💎 Schema-Central Design

The Speculator AST JSON Schema is the single source of truth. All pipeline outputs are validated against this schema, ensuring that downstream tools (like @openuji/render-respec) can rely on a stable, typed data model.

Core Node Types

  • Document: Root container with metadata and indexes.
  • Section: Hierarchical grouping with nested sections.
  • Block: Paragraphs, headings, code blocks, lists, tables.
  • Inline: Text, emphasis, definitions (dfn), cross-references (xref).

🚀 Usage

import { speculate, corePlugins, NodeFileProvider } from "@openuji/speculator";

const result = await speculate({
  entry: "spec/index.md",
  plugins: [...corePlugins],
  fileProvider: new NodeFileProvider(),
});

console.log(result.workspace.documents[0].ast);

🛠️ Development & Playbook

Parser Module Convention

Code that maps IR (hast/mdast) to SpecAST lives in src/parse/ following the <NodeTypes><Format>Parser naming pattern (e.g., HeadingsHtmlParser).

Plugin Contract

Postprocess plugins implement specific phase handlers (transform, resolve, index, compute) with deterministic ordering weights.

📖 Further Reading