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

v0.2.0

Published

This plugin allows the Tabnas parser to determine the path to values.

Readme

@tabnas/path (Tabnas parser plugin)

This plugin adds property-path tracking to the Tabnas parser so that rule actions can see the path (keys and indices) leading to the current value.

npm version build

| Voxgig | This open source module is sponsored and supported by Voxgig. | | ---------------------------------------------------- | --------------------------------------------------------------------------------------- |

Install

npm install @tabnas/parser @tabnas/json @tabnas/path

The Tabnas engine ships no grammar of its own — you bring a grammar plugin that defines the val / map / pair / list / elem rules (here, @tabnas/json). Install the grammar first, then Path on top.

Tiny example

Path populates r.k.path for every value; a second plugin reads it. Here each scalar is tagged <value:path> and each map gets a $ of <path>:

const { Tabnas } = require('@tabnas/parser')
const { json } = require('@tabnas/json')
const { Path } = require('@tabnas/path')

const capture = (tn) => {
  tn.rule('val', (rs) =>
    rs.ac(false, (r) => {
      if (null === r.node || 'object' !== typeof r.node) {
        r.node = `<${r.node}:${r.k.path}>`
      } else if (!Array.isArray(r.node)) {
        r.node.$ = `<${r.k.path}>`
      }
    }),
  )
}

const parser = new Tabnas({ plugins: [json] }).use(Path).use(capture)
const out = parser.parse('{"a":[1,2]}')

out.a     // => ['<1:a,0>', '<2:a,1>']
out.a[0]  // => '<1:a,0>'

Each scalar carries its full path: 1 lives at a, 0 and 2 at a, 1.

Documentation

The docs follow the Diátaxis four-quadrant structure:

  • Tutorial — zero to a working path-tracking parser, step by step.
  • How-to guides — recipes: read the path, keep a copy, seed a base path, classify segments.
  • Reference — exports, options, the Rule.k keys, the function refs, meta input.
  • Concepts — how it works, the engine relationship, the array-pool / mutability trade-off.

The Go port lives in ../go/ with its own docs.

License

MIT. Copyright (c) Richard Rodger.