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

@ferrow/text-chunker

v1.0.0

Published

Boundary-respecting text chunking for RAG — sentence/paragraph/markdown-heading aware, configurable overlap, per-chunk metadata, zero runtime dependencies.

Readme

text-chunker

CI

Boundary-respecting text chunking for RAG pipelines — sentence, paragraph, or markdown-heading aware, configurable overlap, per-chunk metadata, zero runtime dependencies, strict TypeScript.

Quickstart

import { chunkText } from "text-chunker";

const doc = `# Getting Started

This library helps you chunk documents for RAG pipelines.

## Usage

Longer usage content goes here...`;

const chunks = chunkText(doc, {
  boundary: "markdown",
  targetSize: 300,
  sizeUnit: "chars",
  overlap: 30,
});

for (const c of chunks) {
  console.log(c.index, c.headingPath, c.text.length, c.hardSplit);
}

API

chunkText(text, options?)

  • text: string
  • options.boundary?: "sentence" | "paragraph" | "markdown" — default "paragraph".
  • options.targetSize?: number — default 500.
  • options.sizeUnit?: "chars" | "tokens" — default "chars".
  • options.overlap?: number — overlap between consecutive chunks, in sizeUnit. Default 0.
  • Returns Chunk[].

Each Chunk is:

interface Chunk {
  text: string;
  index: number;
  start: number;   // char offset in the source text
  end: number;      // char offset, exclusive
  headingPath: string[]; // markdown heading stack; [] for non-markdown input
  hardSplit: boolean;    // true if a unit exceeded targetSize and was force-split
}

estimateTokens(text)

Tiny built-in chars / 4 estimator used only when sizeUnit: "tokens". For a fuller heuristic (CJK, code density, per-model calibration), see the sibling token-estimator package.

Limits

  • Chunks never split mid-sentence/paragraph/section unless a single unit alone exceeds targetSize — in that case it is hard-split and flagged hardSplit: true. Set a generous targetSize if you never want hard splits.
  • markdown boundary mode splits on heading lines only, not sub-paragraphs within a section — a whole section under a heading is one unit until it exceeds targetSize.
  • The token estimator is a rough chars/4 heuristic, not a real tokenizer.
  • Sentence splitting is regex-based (./!/? boundaries) and does not handle abbreviations, decimal numbers, or non-Latin punctuation specially.
  • Overlap is measured in the same unit as targetSize and is built from whole boundary units carried from the tail of the previous chunk — it will not exceed overlap but may be smaller than requested if the last unit alone is larger than overlap.

Part of the ferrow-toolkit collection · Sponsored by Ferrow