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

oxidocs

v0.1.0

Published

WebAssembly bindings for Oxidocs — Word-compatible .docx parsing, layout, rendering and PDF export

Readme

oxidocs

A Word-compatible .docx layout and rendering engine, compiled to WebAssembly — parse, lay out, edit and PDF-export Microsoft Word documents entirely in the browser (or any JS runtime).

Early development. The API is 0.x and unstable; development happens in the open at https://gitlab.com/Ryujiyasu/oxi. The engine core is also published on crates.io as oxidocs.

What it does

  • Parses OOXML WordprocessingML (.docx) into a structured document model
  • Lays out documents with a line/page model measured against Microsoft Word's own rendering — including Japanese typography: kinsoku line breaking, document grid (docGrid), ruby, vertical writing
  • Edits text with incremental re-layout, and exports to PDF (embedded CJK fonts included)

How fidelity is measured

Layout is verified continuously against Word as the oracle: per-paragraph pagination equality (100% on the current 87-document corpus of real-world Japanese government/legal documents) and per-page SSIM pixel comparison.

Usage

import init, { parse_document, layout_document, docx_to_pdf } from 'oxidocs';

await init();
const bytes = new Uint8Array(await file.arrayBuffer());
const doc = parse_document(bytes);      // structured document model
const pages = layout_document(bytes);   // laid-out pages (positions in pt)
const pdf = docx_to_pdf(bytes);         // Uint8Array (PDF)

License

MIT OR Apache-2.0 (bindings). The engine core is MPL-2.0.