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

@promptc/parser

v0.0.2

Published

Parsers (markdown / XML / plain) into promptc IR.

Downloads

262

Readme

@promptc/parser

The front end of the promptc compiler — turns markdown, XML, or plain-text prompts into a typed PromptIR (defined in @promptc/ir).

Every entry point is a pure function of the input string: same bytes in produces the same IR out. No I/O, no RNG. This is the basis for the compile path's overall determinism guarantee.

Install

bun add @promptc/parser
# or
npm install @promptc/parser

Quick API

import { parse, parseAuto, parseMarkdown, parseXml, parsePlain } from "@promptc/parser";

// Format-routed:
const ir1 = parse(source, { format: "markdown" });
const ir2 = parse(source, { format: "auto" });

// Direct:
const ir3 = parseMarkdown(source);
const ir4 = parseXml(source);   // throws ParseError on malformed input
const ir5 = parsePlain(source);

parse(source, { format: "auto" }) runs the lightweight format detector (no LM, no heuristics that depend on locale or environment) and dispatches to the right per-format parser.

What's in here

  • parseMarkdown — heading-and-list driven layout, fenced code, simple example/output-schema markers.
  • parseXml<task>, <context>, <example>, etc. tag layout. Throws ParseError on malformed input.
  • parsePlain — minimal plain-text fallback (one big task section).
  • parseAuto — format detector + dispatch.
  • ErrorsParseError with byte/line/column location info.

Errors

Malformed XML or invalid plain-text shapes throw ParseError, which carries a location field ({ line, column, byteOffset }) suitable for piping into editor diagnostics.

Links

License

Apache-2.0. See LICENSE.