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

@docx-pages/fonts

v0.2.0

Published

Freely redistributable faces whose metrics twin the ones documents usually name, for laying out without the real fonts.

Downloads

287

Readme

@docx-pages/fonts

Freely redistributable faces whose metrics twin the ones documents usually name, so @docx-pages/core can lay a document out when the named fonts cannot be supplied: Carlito for Calibri, Caladea for Cambria, and the Liberation family for Arial, Times New Roman and Courier New. Advance widths match glyph for glyph, so lines break where the named face would have broken them.

import { bestEffortMetrics, layOutDocument, openDocx, readFaceShapes } from "@docx-pages/core";
import { defaultFaces } from "@docx-pages/fonts"; // or "@docx-pages/fonts/node" off a disk

const pkg = openDocx(bytes);
const faces = bestEffortMetrics(suppliedFaces, await defaultFaces(), readFaceShapes(pkg));
const layout = layOutDocument(pkg, faces); // every stand-in comes back out of faces.substitutions()

A document naming a face with no twin falls to a default of the shape the document's own font table gives the name: Open Sans for a sans, carried for its looks rather than its widths, since a name with no twin gets no right widths from anyone. A name nothing classifies falls to Caladea, because Word's own last resort for a name it cannot place is Cambria.

The font files keep their own licenses, committed beside them under fonts/.

One consumer note: the pack finds its files beside its own module, so a dev server that prebundles dependencies has to leave these two alone. Under Vite that is

optimizeDeps: {
  exclude: ["@docx-pages/viewer", "@docx-pages/fonts"];
}

and vite build needs nothing.