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

piece-buffer

v0.2.0

Published

A lightweight implementation of a Piece Buffer - an efficient data structure for storing and modifying text.

Readme

Piece Buffer

npm version GitHub Workflow Status

This is a lightweight implementation of a Piece Buffer - an efficient data structure for storing and modifying text.

Installation

To install with npm:

npm install piece-buffer

or yarn:

yarn add piece-buffer

Basic usage

Here's a small example that creates an editor, inserts some text in the middle, and appends some text to the end.

const pb = require("piece-buffer");
const editor = pb.createEditor("Hello World.");
editor.insert(6, "Cool ");
editor.append(" Goodbye!");
// Prints "Hello Cool World. Goodbye!"
console.log(editor.toString());

Positions and lines

The Piece Buffer editor keeps track of lines in the text.

The main mutation operations of an editor (delete() and insert()) both take a position as the first parameter. This can simply be a character offset, or it can be a line and column number (both of which are zero-based).

For example:

const pb = require("piece-buffer");
const editor = pb.createEditor("Hello\nPiece\nBuffer\n");
editor.insert({line: 1, column: 5}, "meal");
// Prints "Hello\nPiecemeal\nBuffer\n"
console.log(editor.toString());

It's convenient to iterate lines:

const pb = require("piece-buffer");
const editor = pb.createEditor("Hello\nPiece\nBuffer\n");
// Prints:
// Hello
// Piece
// Buffer
for (const line of editor.lines()) {
  console.log(line)
}

It's also convenient to iterate lines matching an expression. The iterator will yield back an array containing the regular expression match array, the whole line that matched, and the line number:

const pb = require("piece-buffer");
const editor = pb.createEditor("Hello\nPiece\nBuffer\n");
// Prints:
// Line 1 (Piece) matched: P
for (const line of editor.linesMatching(/^P/)) {
  console.log(`Line ${line[2]} (${line[1]}) matched: ${line[0][0]}`)
}

Selections

Selections are a useful way to find and replace or delete parts of a document efficiently. They behave a lot like the cursor selection in a text editor.

const pb = require("piece-buffer");
const editor = pb.createEditor("Hello World.");
const selection = editor.createSelection();
selection.selectFirst("World");
selection.replace("Piece Buffer");
// Prints "Hello Piece Buffer."
console.log(editor.toString());

TODO: more documentation

Performance

TODO: Compare performance to basic strings, write up benchmark.


This is not an officially supported Google product.