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

@tabnas/gbnf

v0.1.8

Published

llama.cpp GBNF grammar compiler for the tabnas parser.

Readme

@tabnas/gbnf

GBNF grammar compiler for the tabnas parser.

Takes GBNF source (the llama.cpp dialect — ::= and |, case-sensitive literals, a mandatory root) and emits a tabnas GrammarSpec. Installed on an engine, the spec parses inputs in that grammar and builds a {rule, src, kids} AST — so you can answer "does this string match my grammar?" without loading a model.

Install

npm install @tabnas/parser @tabnas/bnf @tabnas/gbnf

Use

const { Tabnas } = require('@tabnas/parser')
const { gbnf } = require('@tabnas/gbnf')

const tn = new Tabnas({ plugins: [gbnf] })
tn.gbnf(`root ::= "hi" | "hello"`)

tn.parse('hi') // => ({ rule: 'root', src: 'hi', kids: [] })

Exact by construction

GBNF is scannerless: the grammar accounts for every character, including the spaces. The engine's defaults are JSON-shaped and lenient, so the emitted spec turns them off — empty ignore set, no space/line/comment/ string/number/text matchers. What is left is the grammar's own fixed tokens (its literals) and match tokens (its classes).

const { Tabnas } = require('@tabnas/parser')
const { gbnf } = require('@tabnas/gbnf')

const tn = new Tabnas({ plugins: [gbnf] })
tn.gbnf(`root ::= "a" "b"`)

tn.parse('ab').src // => 'ab'

let rejected = false
try { tn.parse('a b') } catch (e) { rejected = true }
rejected // => true

Whether the empty input is in the language is settled at compile time, because the engine short-circuits '' before any rule runs: the compiler walks the IR for a derivation of the empty string from root and emits lex: { empty: … } to match.

const { gbnfConvert } = require('@tabnas/gbnf')

gbnfConvert(`root ::= "x"`).options.lex  // => ({ empty: false, relex: true })
gbnfConvert(`root ::= "x"*`).options.lex // => ({ empty: true, relex: true })

The validator CLI

gbnf-check installs with the package: compile a grammar, check samples against it, read the exit code (0 all accepted, 1 a rejection, 2 no compile, 3 usage). --json emits a stable report for tooling and AI agents.

npx gbnf-check grammar.gbnf sample.txt
npx gbnf-check grammar.gbnf --text 'candidate' --json

See doc/reference.md for options, exit codes, and the JSON report shape.

What this package owns

Only the notation. The compilation itself — desugaring repetition into helper rules, left-recursion elimination, probe dispatch, literal lifting, token allocation, first-set analysis, chain emission — lives in @tabnas/bnf, shared with the ABNF and EBNF front-ends:

GBNF text ──parseGbnf──▶ Grammar IR ──emitGrammarSpec──▶ GrammarSpec

src/converter.ts is the first arrow (a tabnas grammar that reads GBNF, plus the terminal decoders and the lexer settings the spec carries); src/gbnf.ts is the plugin facade.

Documentation

Four-quadrant Diátaxis docs:

  • tutorial.md — learning-oriented: zero to a working parser, step by step.
  • guide.md — task-oriented recipes for real problems.
  • reference.md — the exact API and GBNF syntax supported.
  • concepts.md — how the compiler works and why.
  • known-gaps.md — where this and llama.cpp diverge, and what causes each divergence.

License

MIT. Copyright (c) Richard Rodger.