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

krbc

v1.0.0

Published

Binary container format for key-addressable byte ranges with cross-platform support for Browser and Node.js

Downloads

14

Readme

KRBC — Keyed Range Binary Container

KRBC is a small binary container format and utility library for working with key-addressable byte ranges in large binary files.

It is designed to make partial read/write simple and predictable across Browser and Node.js, without imposing any structure on the stored data.

KRBC does not care what your data is. It only maps:

key[]  ->  [byteFrom, byteTo)

What KRBC is good for

  • Partial loading of large binary files
  • Tile / chunk / bbox based data access
  • CAD, GIS, map, or geometry data
  • Streaming binary assets
  • Any scenario where data is split into independent ranges

Installation

npm install krbc

Data model

KRBC works with an array of entries.
Each entry consists of a key and a binary payload.

Keys are fixed-size arrays. Their meaning is entirely application-defined.

Ranges are always stored as [from, to) (end-exclusive).

Browser data example

const textEncoder = new TextEncoder()

const data = [
	{
		key: [ 0, 1, 2 ],
		data: textEncoder.encode( "Hello" ),
	},
	{
		key: [ 3, 4, 5 ],
		data: textEncoder.encode( "World" ),
	}
]

Node.js data example

const data = [
	{
		key: [ 0, 1, 2 ],
		data: Buffer.from( "Hello" ),
	},
	{
		key: [ 3, 4, 5 ],
		data: Buffer.from( "World" ),
	}
]

Browser example

Write (OPFS)

import * as KRBC from "krbc"

const codec = KRBC.createElementCodec( "int32" )

await KRBC.writeOPFS( "example.krbc", data, codec )

Export file (download)

await KRBC.exportFile( "example.krbc" )

Read

import * as KRBC from "krbc"

const codec = KRBC.createElementCodec( "int32" )
const index = await KRBC.readIndex( "/example.krbc" )

for ( const e of index.entries ) {

	const key = KRBC.unpackKey( e.key, codec )
	const bytes = await KRBC.fetchRange( "/example.krbc", e.range )

	console.log( key, new TextDecoder().decode( bytes ) )
}

Node.js example

Write

import * as KRBC from "krbc"

const codec = KRBC.createElementCodec( "int32" )

KRBC.writeFile( "example.krbc", data, codec )

Read

import * as KRBC from "krbc"

const codec = KRBC.createElementCodec( "int32" )
const index = KRBC.readIndex( "example.krbc" )

for ( const e of index.entries ) {

	const key = KRBC.unpackKey( e.key, codec )
	const bytes = KRBC.readRange( "example.krbc", e.range )

	console.log( key, bytes.toString() )
}

Notes

  • Ranges are always [from, to) (end-exclusive)
  • Index entries may overlap or duplicate
  • KRBC does not validate or interpret keys
  • Binary layout is stable and deterministic