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

z-parser

v1.7.1

Published

Client SDK for the z-parser document extraction service — bytes in, RAG-ready Markdown out (PDF/OCR, Office, images, manuscripts, audio/video, EPUB, e-mail).

Readme

z-parser (Node SDK)

Node client for the z-parser document-extraction service: bytes in, RAG-ready Markdown out. Scanned PDFs (SOTA OCR + vision escalation), Office, spreadsheets, images, charts, manuscripts, EPUB, e-mail, audio/video transcription.

Zero dependencies — Node ≥ 18 (built-in fetch).

npm install z-parser
# no service running yet? one container, one key:
docker run -d -p 4056:4056 -e MISTRAL_API_KEY=xxx yatchiyax/z-parser
import { ZParser } from "z-parser";

const zp = new ZParser("http://localhost:4056");   // or $Z_PARSER_URL
const doc = await zp.parse("rapport.pdf");         // path, or bytes + {filename}
console.log(doc.parser, doc.numChars);             // "mistral-ocr+figures(2)" 48213
console.log(doc.text);

const pdf = await zp.renderPdf("deck.pptx");                  // Office → viewable PDF
const figs = await zp.images("catalogue.pdf", { mode: "artwork" });

CLI: npx z-parser contract.pdf -o contract.md

Pick your provider from the client — Mistral, Ollama (100 % local), vLLM, Hugging Face or any OpenAI-compatible vision endpoint, per client or per call:

const zp = new ZParser(undefined, {
  visionProvider: "openai",
  visionBaseUrl: "http://host.docker.internal:11434/v1",  // Ollama, seen FROM the server
  visionModel: "llama3.2-vision",
  docVision: true,          // PDFs through local vision too → fully offline
});
await zp.parse("scan.pdf", { visionModel: "qwen2.5-vl" });  // per-call override wins

// Shorthand + quality levers (mirror the server's .env):
await new ZParser().parse("dossier.pdf", {
  visionProvider: "mistral",   // openai dialect on api.mistral.ai, server key applies
  ocrEscalate: true,           // weak OCR pages re-read by vision (manuscripts)
  describeFigures: true,       // embedded charts/diagrams described on their page
});

Safety contract: a caller-chosen visionBaseUrl never receives the server's own API keys — bring your own key (visionApiKey) or none. With no provider params, the server's configuration applies.

Errors are explicit: ZParserError carries the service's status (unsupported / error). Timeout defaults to 15 minutes (timeout option) — large OCR jobs are slow by nature.

The service itself (Docker, one container), its benchmark and the Python/Rust SDKs live in the main repository.