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

indent-parser

v0.2.0

Published

Parser for a generic, human-friendly, indentation-based tree markup language (XML-light), Indent Markup Language (.inml).

Readme

indent-parser

A typescript parser for Indent Markup Langauge.

API

import { parse, parseFile } from "indent-parser";

const { roots } = parse(source);
// roots: IndentNode[]
// IndentNode = { kind: string; value?: string | number | boolean | RefValue; attrs: Record<string, AttrValue>; children: IndentNode[] }
// AttrValue = string | number | boolean | RefValue
// RefValue = { type: "ref", raw: string }

// Reads `entry.inml` from disk and resolves any include lines within it
// (and transitively within included files) before building the tree.
const { roots: rootsFromDisk } = parseFile("entry.inml");

parse and parseFile throw IndentParseError (with line and, for parseFile, a file property) on malformed input.

Wire format

encodeWireFormat/decodeWireFormat convert between normal 4-space-indented Indent source and a compact single-line "wire format" that replaces newline + indentation-change with escape sequences. This is a pure text transform (no tokenizing/parsing) meant for transmitting .inml structure without embedded raw newlines.

import { encodeWireFormat, decodeWireFormat } from "indent-parser";

const wire = encodeWireFormat(source);
const roundTripped = decodeWireFormat(wire);
// roundTripped === source (modulo normalizing line endings to `\n`)

Escape sequences, one character per depth level crossed:

  • \+ — indent one level deeper than the previous line.
  • \- — dedent one level shallower than the previous line.
  • \= — same depth as the previous line (a sibling); no indentation change needs to be communicated, but the marker is still required so the wire format never contains a raw embedded newline.

Runs of \+/\- are used for multi-level jumps, e.g. going from depth 0 to depth 2 encodes as \+\+, and back down to depth 0 as \-\-. Blank lines and comment-only (;...) lines carry no indentation of their own, so they are encoded as a same-depth (\=) transition.

decodeWireFormat throws IndentParseError if a \- run would dedent past depth 0.

Development

npm install
npm run build
npm test