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

@pdfmuse/core

v0.1.12

Published

Deterministic PDF/DOCX parser for RAG / LLMs — WebAssembly build (browser + Node).

Readme

@pdfmuse/core

WebAssembly build of pdfmuse — a deterministic PDF/DOCX parser for RAG / LLMs. No native binary: the same package runs in the browser (the file never leaves the tab) and on Node, including CommonJS-only hosts where a .node addon is not an option.

npm i @pdfmuse/core

Usage

Browser / ESM — the wasm is fetched, so init() is async:

import init, { to_text, parse } from "@pdfmuse/core";
await init();

const bytes = new Uint8Array(await file.arrayBuffer());
const text  = to_text(bytes);                  // plain reading-order text
const doc   = JSON.parse(parse(bytes));        // full IR: chars/blocks with bboxes

Node / CommonJS — the wasm is read from disk and instantiated at require time, so there is no init() step:

const { to_text, to_markdown, parse } = require("@pdfmuse/core");

const bytes = new Uint8Array(require("fs").readFileSync("resume.pdf"));
const md    = to_markdown(bytes);              // headings + tables preserved

Node ≥ 18. The module uses the reference-types and multivalue wasm proposals, which Rust enables by default for wasm32-unknown-unknown and current wasm-bindgen requires. Node 16 rejects it with invalid value type 'externref', Node 14 with return count of 4 exceeds internal limit of 1.

Use this build when a native addon won't load — bundled serverless runtimes, sandboxed platforms, anywhere the deploy artifact is JS-only. If you can ship a binary, @pdfmuse/node is faster.

Extracts text with exact coordinates, tables and structure; deterministic, byte-identical to the Python/Node/Rust bindings. Scanned/image-only pages return a NeedsOcr warning to hand off server-side.

  • Live playground: https://casperkwok.github.io/pdfmuse/
  • Docs & source: https://github.com/casperkwok/pdfmuse

MIT OR Apache-2.0