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

@openexam/parser

v0.1.0

Published

Reference parser: OpenExam source (Markdown + directives) to OEAST, spec 0.1.

Readme

@openexam/parser

Reference parser. Turns an OpenExam source file (.oex.md — Markdown + directives + YAML frontmatter) into an OEAST Document, targeting spec 0.1 (M1).

This is the conformance baseline per ADR-023 §6: where the spec text and the parser disagree, the parser wins, and the spec text is corrected in the next patch release.

Public API

import { parse } from '@openexam/parser';
import type { Document } from '@openexam/sdk';

const source = await fs.readFile('assignment.oex.md', 'utf8');
const document: Document = parse(source);

parse throws ParseError on any rejected input. The error carries line, column, and message.

Spec subset

0.1 is deliberately tiny — see spec/0.1/grammar.md. The parser rejects anything outside that subset (math, images, tables, fenced code, links, ordered lists, etc.) with location-pointing errors so authors don't accidentally rely on shapes that may change in 0.2.

Implementation choices

  • Hand-written. The 0.1 subset is small enough that depending on unified/remark/remark-directive would buy us less control over rejected-construct error messages than it costs in dep weight and parser-config gymnastics.
  • yaml (Eemeli Aro) for frontmatter parsing.
  • No runtime JSON Schema validator: the parser produces typed OEAST nodes whose shapes match the SDK types by construction. Tests validate the output against spec/0.1/oeast.schema.json for defense-in-depth.

License

Apache-2.0. See LICENSE and the repository root ../../LICENSE.