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

@microscope-js/renderer-docx

v0.1.5

Published

DOCX (Word) renderer for microscope-js (uses mammoth + DOMPurify)

Readme

@microscope-js/renderer-docx

npm Bundle Types Provenance

Renders .docx (Word) documents in the browser for microscope-js, via mammoth.js. The HTML mammoth produces is run through a hardened DOMPurify profile before it ever touches the DOM.

Install

pnpm add @microscope-js/renderer-docx

Use

import { createRegistry, mount } from '@microscope-js/core';
import { docxRenderer } from '@microscope-js/renderer-docx';

const registry = createRegistry([docxRenderer]);
await mount({ source: file, container, registry });

Or with React:

<Viewer
  source={file}
  registry={useRegistry([docxRenderer])}
  options={{ maxBytes: 32 * 1024 * 1024 }}
/>

Options

| Option | Default | Description | | ----------- | ------------------ | -------------------------------------------------------------------------- | | maxBytes | 64 * 1024 * 1024 | Reject docx files larger than this (MicroscopeError('TOO_LARGE')) | | styleMap | mammoth defaults | Custom style map — map Word styles to HTML elements |

Format support

  • .docx (Word 2007+) — primary target, well supported by mammoth
  • .doc (legacy binary) — best-effort; mammoth has limited coverage of the older format

Security model

  • Every HTML node mammoth emits is sanitized via the shared DOMPurify profile from @microscope-js/utilsscript, iframe, form, every on* attribute, data: URIs (except safe image types), and unknown protocols are stripped.
  • All anchors are rewritten to rel="noopener noreferrer" + target="_blank".
  • The size cap defends against zip-bomb-class inputs.
  • mammoth + this renderer run only in the user's browser. The document never leaves the tab.

See also

License

MIT