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

usfm3

v0.2.0

Published

Error-tolerant USFM 3.x parser with USJ, USX, and USFM output

Readme

usfm3

usfm3 is the JavaScript / TypeScript package for the Rust usfm3 parser.

It exposes a staged API so browser, Node, and editor integrations can stay on the cheapest representation they need.

Installation

npm install usfm3

In browsers:

import init from "usfm3";
await init();

Quick Start

import { parse, parseAst, parseCst, tokenize } from "usfm3";

const parsed = parse(usfmText);

const tokens = tokenize(usfmText);
const cst = parseCst(usfmText);
const astDocument = parseAst(usfmText, { diagnostics: true });

const ast = parsed.ast();
const sourceMap = parsed.sourceMap();
const diagnostics = parsed.diagnostics();

const usj = parsed.toUsj();
const usjWithSpans = parsed.toUsj({ spans: true });
const usx = parsed.toUsx();
const usfm = parsed.toUsfm();
const vref = parsed.toVref();

parsed.free();

API

parse(usfm: string, options?: { diagnostics?: boolean }): ParsedDocument

Returns a lazy parsed handle.

parseCst(usfm: string): any

Returns a JSON-friendly CST tree.

parseAst(usfm: string, options?: { diagnostics?: boolean }): any

Returns:

{
  ast: ...,
  sourceMap: ...,
  diagnostics?: Diagnostic[]
}

tokenize(usfm: string): any[]

Returns token spans suitable for editor tooling.

ParsedDocument

  • cst(): any
  • ast(): any
  • sourceMap(): any
  • diagnostics(): Diagnostic[] | undefined
  • toUsj(options?: { spans?: boolean }): any
  • toUsx(): string
  • toUsfm(): string
  • toVref(): Record<string, string>
  • free(): void

Notes

  • tokenize() and parseCst() are cheaper than materializing the AST.
  • Diagnostics are only computed when diagnostics: true is requested.
  • Diagnostics are a flat list.
  • AST nodes do not carry spans.
  • toUsj({ spans: true }) derives inline span data from the source map.

License

MIT