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

@office-kit/docx-preview

v0.1.0

Published

Browser preview for word-kit .docx documents.

Readme

@office-kit/docx-preview

Browser-side read-only preview for .docx documents produced (or opened) by @office-kit/docx.

Status

Stable. Wraps the OSS docx-preview (Apache-2.0) renderer behind word-kit's function-API surface. The wrap is intentional and final — see docs/PLAN-PREVIEW.md for why we are not re-implementing the renderer in-house.

If you hit a fidelity bug, please file it against docx-preview upstream first; we follow that project's releases and bump the peer-dep promptly.

Install

npm install @office-kit/docx @office-kit/docx-preview
# or: pnpm add @office-kit/docx @office-kit/docx-preview

@office-kit/docx-preview declares @office-kit/docx and docx-preview as runtime dependencies. Both are ESM-only.

Usage

import { openDocx } from "@office-kit/docx";
import { previewToDOM } from "@office-kit/docx-preview";

const bytes = /* Uint8Array | Blob | ArrayBuffer */;
const doc = openDocx(bytes);

const handle = await previewToDOM(
  doc,
  document.getElementById("preview")!,
  {
    classPrefix: "wk-",          // CSS namespace (default "wk-")
    inWrapper: true,             // wrap each page in a scrolling block
    breakPages: true,            // honour source-declared page breaks
    renderFonts: true,           // inject @font-face from the docx
    experimentalComments: false, // upstream-experimental
    experimentalChanges: false,  // upstream-experimental
  },
);

// …later, when you no longer need the preview:
handle.dispose();

previewToDOM accepts:

  • a Docx value returned by createDocx / openDocx / clone / fromBlob from @office-kit/docx, or
  • raw bytes — Uint8Array, Blob, or ArrayBuffer.

It returns a Handle with a single dispose() method that detaches the rendered DOM and releases internal references. dispose() is idempotent.

What renders well

  • Body text + paragraph styling (bold, italic, underline, color, font, size).
  • Custom paragraph / character / table styles defined in styles.xml. Custom styles your code sets through addStyle(doc, …) work the same as styles imported from a hand- designed Word template.
  • Lists (bullet + numbered).
  • Tables — borders, shading, header rows.
  • Inline images.
  • Hyperlinks.
  • Headers / footers — drawn at the top / bottom of each page.
  • Footnotes / endnotes — flat tail block.

Known gaps (inherited from docx-preview v0)

  • No live re-pagination. Pages are drawn at source-declared breaks (<w:br w:type="page"/>, <w:lastRenderedPageBreak/>). Edits to the doc don't reflow page boundaries.
  • No field evaluation. TOC, PAGE, NUMPAGES etc. show their cached display values when present, otherwise the field instruction.
  • Tab stops / list edge cases / empty-paragraph height — known upstream issues.

The v1 native renderer will address the long tail one feature area at a time; see docs/PLAN-PREVIEW.md for the order.

Out of scope

  • Editing. Read-only by design.
  • Pixel-perfect Word rendering. HTML/CSS cannot replicate every WML page semantic.
  • PDF rendering. Document the LibreOffice headless → pdf.js recipe externally; we don't ship it.

License

MIT