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

@harrisonwang/spoor

v0.8.18

Published

Native Node.js bindings for the spoor document engine

Readme

@harrisonwang/spoor

Native Node.js bindings for the spoor document engine.

const { parseBytes } = require('@harrisonwang/spoor');

const result = parseBytes(Buffer.from('hello\n'), { sourceName: 'note.txt' });
for (const warning of result.warnings) {
  console.warn(warning.code, warning.location);
}

Native addons are distributed as optional platform packages. Thrown spoor errors expose code, reason, hint, recoverable, and stage. Successful parses can still contain typed integrity warnings; agents must inspect result.warnings.

Tables: narrowing and pagination

For CSV/XLSX, parseBytes accepts the same narrowing options as the CLI, so pipelines can page through full tables instead of the default 100-row preview:

// A slice by inclusive 1-based [first, last] row range (mutually exclusive with limit/offset)
parseBytes(data, { sourceName: 'data.xlsx', sheet: 'Sheet1', rows: [5, 104] });

// Or paginate by limit/offset and keep only some columns
parseBytes(data, { sourceName: 'data.xlsx', columns: ['分类', '金额'], limit: 100, offset: 200 });

PDFs: page ranges

For page-oriented PDFs, pass pages (inclusive 1-based) to parse only a slice and avoid reading a large document end to end:

parseBytes(data, { sourceName: 'report.pdf', pages: [1, 3] }); // only pages 1–3

Extracting embedded media

Resolve a safe media URI emitted in the output (DOCX images, extractable PDF images) to a Buffer for handing to an external vision model:

const { extractMedia } = require('@harrisonwang/spoor');

const image = extractMedia(data, 'spoor://docx/part/word/media/image1.png', { sourceName: 'report.docx' });