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

@raintree-technology/docpull-sdk

v6.5.0

Published

TypeScript SDK for reading docpull context packs and running the docpull CLI

Readme

@raintree-technology/docpull-sdk

TypeScript SDK for docpull. It reads local context packs (the v3 pack contract) and runs the docpull CLI from Node or Bun. Reading a pack never touches the network; fetching requires the docpull CLI on PATH.

Install

bun add @raintree-technology/docpull-sdk   # or: npm install @raintree-technology/docpull-sdk

Read a pack

import { readCorpusManifest, readDocuments, readPack } from "@raintree-technology/docpull-sdk";

const manifest = await readCorpusManifest("./packs/example");
console.log(manifest.record_count, manifest.records[0]?.url);

// Stream records one line at a time.
for await (const record of readDocuments("./packs/example")) {
  console.log(record.document_id, record.token_count);
}

// Or load everything at once.
const pack = await readPack("./packs/example");
console.log(pack.documents.length);

readDocuments prefers documents.ndjson and falls back to documents.jsonl. Types (CorpusManifest, ManifestRecord, DocumentRecord) mirror the field names written by the Python side and keep unknown fields as forward-compatible metadata.

Run the CLI

import { fetchToPack, runDocpull } from "@raintree-technology/docpull-sdk";

// docpull https://example.com/docs -o ./packs/example --budget 0
await fetchToPack("https://example.com/docs", "./packs/example", { budget: 0 });

// Any other subcommand.
const result = await runDocpull(["pack", "validate", "./packs/example"]);
console.log(result.stdout);

Commands are spawned with an argument array and shell: false. A non-zero exit rejects with a DocpullCliError that carries exitCode and stderr.

Development

bun install        # from the repo root
bun test           # from sdk/js
bun run typecheck  # tsc --noEmit

License

MIT