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

xron-format

v0.4.1

Published

Extensible Reduced Object Notation — lossless data serialization achieving ~80% token reduction for LLM contexts

Readme

xron-format

Extensible Reduced Object Notation — a lossless, drop-in replacement for JSON.stringify/JSON.parse that cuts LLM token usage by removing the structural overhead JSON pays on every request: repeated keys, repeated values, and punctuation a tokeniser has to spend tokens on.

XRON.parse(XRON.stringify(data)) deep-equals data. Nothing is dropped, summarised, or approximated — it's an algorithmic encoder, not an LLM.

npm version License

Install

npm install xron-format

Usage

import { XRON } from 'xron-format';

const data = [
  { id: 1, name: 'Alice', dept: 'Sales' },
  { id: 2, name: 'Bob', dept: 'Engineering' },
  { id: 3, name: 'Carol', dept: 'Sales' },
];

const xron = XRON.stringify(data);
// @v2
// @S A: id, name, dept
// @D: Sales
// @N3 A
// 1, Alice, $0
// 2, Bob, Engineering
// 3, Carol, $0

const restored = XRON.parse(xron);
// restored deep-equals data

How much smaller is it?

Depends on how much of your payload is structure versus information — XRON removes repeated keys and repeated values, so it can't shrink data that's already unique. Measured with the real o200k_base tokenizer:

| Your data looks like | Token reduction | |---|---:| | Identical repeated rows, long string values | up to 91% | | Wide tables, small vocabulary (30 cols) | ~80% | | Boolean/flag matrices (20 cols) | ~71% | | Typical business records (6 fields) | ~48% | | Unique UUIDs or unique prose | ~21% |

Full methodology and per-shape figures: BENCHMARKS.md.

API

XRON.stringify(value, options?): string

| Option | Type | Default | Description | |---|---|---|---| | level | 1 \| 2 \| 3 \| 'auto' | 2 | Compression level. 'auto' picks whichever level produces the smallest output. | | minCompressSize | number | 0 | Below this JSON byte size, 'auto' returns plain JSON rather than attempting compression. | | tokenizer | 'o200k_base' \| 'cl100k_base' \| 'claude' | 'o200k_base' | BPE tokeniser profile used by Level 3's optimisation pass. |

Guarantees in auto mode: output always round-trips losslessly, and is never larger than JSON.stringify(value).

Throws TypeError on circular references.

XRON.parse(input): any

Parses an XRON string back to the original value.

Verification

Round-trip identity (parse(stringify(x)) === x) is tested against a boundary-focused fuzzing corpus across all four levels, plus three rounds of independently-written adversarial fuzzers. Full bug list, test counts, and methodology: docs/VERIFICATION.md.

License

MIT — see LICENSE.