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-open/doc

v0.15.1

Published

Parse legacy Microsoft Word .doc documents into office-open DocumentOptions — no Microsoft Office required

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

demomacrodemomacro

Keywords

binarydocdocumentlegacymicrosoft-wordofficeoffice-openparseparsertypescriptword

Readme

@office-open/doc

npm version npm downloads npm license

Parse legacy Microsoft Word 97-2003 .doc documents into plain DocumentOptions JSON — no Microsoft Office required.

Features

  • 📄 Document Parsing — Read body content, sections, headers, and footers
  • ✍️ Rich Text — Preserve text runs and character formatting
  • 📊 Tables — Read table structure, rows, cells, and merged cells
  • 🖼️ Images — Extract embedded pictures
  • 🔗 Hyperlinks — Resolve internal and external link targets
  • 🔖 Bookmarks — Read bookmark starts and ends
  • 📝 Fields — Capture field instructions and cached results
  • 🕘 Revisions — Read insertion and deletion revision ranges
  • 🔐 Encrypted Files — Parse password-protected documents with the provided password

This package is parse-only. It does not generate .doc files.

Installation

# pnpm
pnpm add @office-open/doc

# npm
npm install @office-open/doc

# yarn
yarn add @office-open/doc

# bun
bun add @office-open/doc

Quick Start

import { parseDocument } from "@office-open/doc";
import { readFileSync } from "node:fs";

const options = parseDocument(new Uint8Array(readFileSync("input.doc")));

For an encrypted document, provide the password:

const options = parseDocument(data, { password: "secret" });

API

  • parseDocument(data, options?) — read a .doc file into DocumentOptions
  • DocParseOptions — parse-time options, including password
  • DocParseError — thrown for invalid, truncated, unsupported, or encrypted input, with canonical context fields

Errors and Limitations

  • Invalid, truncated, unsupported, and encrypted files throw DocParseError.
  • Unsupported legacy records are skipped without aborting the document; their omissions are visible in canonical context.
  • DOC generation is intentionally unavailable.

Documentation

Related Packages

License