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/debug

v0.2.3

Published

Debug plugin for the tabnas parser — tracing helpers and a describe() method.

Readme

@tabnas/debug

Debug / introspection plugin for the tabnas parser.

It makes a grammar visible: a structured model() and a printable describe() return a description of an instance's installed grammar (rules, tokens, plugins), abnf() re-expresses it as ABNF, and trace logs a parse step by step. A dev/test aid — never a runtime dependency.

Install

npm install @tabnas/parser @tabnas/debug

Use

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

const tn = new Tabnas({ tag: 'demo' })
tn.use(Debug, { print: false, trace: false })

// describe() is the printable form; model() is the structured form.
typeof tn.debug.describe()        // => 'string'

const m = tn.debug.model()
m.tag                             // => 'demo'
m.config.start                    // => 'val'
m.plugins.map((p) => p.name)      // => ['Debug']
Array.isArray(m.rules)            // => true

Structured output — model()

describe() renders the instance as text; model() returns the same information as a typed, JSON-serialisable object (DebugModel):

| field | what it holds | |---|---| | tag | the instance tag | | tokens | { tin, name, fixed? }[] — the token table | | tokenSets | named token sets → member tins | | rules | each rule's open / close alternates as { seq, push, replace, back, counters, groups, action, cond, modifier } | | graph | per-rule push/replace edges (openPush, openReplace, closePush, closeReplace) | | lexer | the lexer matchers (order, matcher, make) | | config | start rule, finish flag, safe-key, and the per-lexer enable flags | | plugins | the applied plugins (name + options) | | abnf | the live grammar rendered as ABNF text |

The grammar-structure fields round-trip through JSON.stringify.

Documentation

  • Tutorial — zero to a working inspection, step by step.
  • How-to guide — focused recipes (diff grammars, capture traces, round-trip ABNF).
  • Reference — the exact exports, options and types.
  • Concepts — how it works and why.

The Go port lives in ../go and tracks this implementation.

License

MIT.