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

@lvcabral/opentype.js

v1.3.9

Published

OpenType.JS (font parser only)

Readme

opentype.js (parse only)

This fork contains a light-weight version of opentype.js that only parses OpenType/TrueType/WOFF font buffers and returns metadata. There are no drawing helpers, glyph constructors, or layout utilities—parse() is the entire public API.

Installation

npm install @lvcabral/opentype.js

Usage

import { readFileSync } from 'fs';
import { parse } from '@lvcabral/opentype.js';

const data = readFileSync('./test/fonts/Roboto-Black.ttf');
const font = parse(data);

console.log(font.unitsPerEm);           // 2048
console.log(font.ascender, font.descender);
console.log(font.tables.head.macStyle);
console.log(font.names.fontFamily.en);

The returned Font object exposes:

  • unitsPerEm, ascender, descender
  • tables.head and tables.hhea objects exactly as they appear in the font tables
  • names, keyed by name ID (e.g. font.names.fullName) with locale entries (BCP-47 tags when available, otherwise the raw 0x#### language ID).

Unsupported table data is ignored. If a required table (head or hhea) is missing the parser throws.

Formats

  • TrueType and OpenType fonts (\x00\x01\x00\x00, true, typ1, OTTO)
  • WOFF containers (tables are decompressed automatically)
  • Format 0/1 name tables encoded in UTF-16

Development

  • npm run build – bundles src/opentype.mjs into dist/opentype.module.js (ESM) and dist/opentype.js with sourcemaps for local debugging
  • npm run dist – produces the minified distributables dist/opentype.module.min.js and dist/opentype.min.js (with sourcemaps)
  • npm test – runs the minimal Mocha suite that loads sample fonts and asserts metadata
  • npm run lint – ESLint over the src/ directory

The parser lives in src/opentype.mjs and only depends on:

  • src/parse.mjs for DataView helpers
  • src/tables/{head,hhea,name}.mjs
  • src/[email protected] for WOFF decompression

Test fonts are stored in test/fonts/. Published consumers load from the generated dist/ artifacts (main/module point there).

Versioning

We use SemVer for versioning.

License

MIT

Thanks

We would like to acknowledge the work of others without which opentype.js wouldn't be possible: