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

text-store

v1.3.1

Published

Super performant text container built upon caches

Downloads

22

Readme

Super performant text container built upon caches

Usage

Install

npm i text-store

Light it up

import TextStore from 'text-store';

const bigA$$File = new TextStore('really big file');

Documentation

You might want it if:

  • You're working with really massive text files, and you will be doing frequent content manipulations here and there

  • You need to frequently convert between line:col based addressing and index based addressing

  • You will be doing both of above, thats the best use case, as TextStore uses caches, and re-computes only whats really needed

  • You have two libraries/apps where one uses line:col based addressing and other uses index based, TextStore can act as glue code

TextStore really shines when an instance is used frequently and not just once or twice. First call to, for example indexToPosition will be significantly slower as that's when TextStore will build it's internal cache, which is used to serve subsequent calls at lightning speeds