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

@ernxst/subfont

v0.1.4

Published

A plugin to purge unused glyphs from your font files to minimise bundle size

Readme

🚀 Font Subsetter

A plugin (likely compatible with your build tool) allowing you to remove unused glyphs from your output font files to improve page-load and time-to-first-byte.

Uses glyphhanger under the hood but with the added functionality of overwriting the build output fonts, rather than creating new ones (and having to create links to/stylesheets for them).

Installation

glyphhanger is also required as a peer dependency:

npm i --save-dev @ernxst/subfont glyphhanger
yarn add -D @ernxst/subfont glyphhanger
pnpm i -D @ernxst/subfont glyphhanger

Usage

Note that this integration only works for static builds, it does nothing (rather than erroring) when SSR is enabled.

You may get unexpected results when using this plugin with dynamically generated content.

Astro

import { defineConfig } from "astro/config";
import subfont from "@ernxst/subfont/astro";

export default defineConfig({
 integrations: [subfont()],
})

Vite

import { defineConfig } from "vite";
import subfont from "@ernxst/subfont/vite";

export default defineConfig({
 plugins: [subfont()],
})

Rollup

import { defineConfig } from "rollup";
import subfont from "@ernxst/subfont/rollup";

export default defineConfig({
 plugins: [subfont()],
})

esbuild

import esbuild from "esbuild";
import subfont from "@ernxst/subfont/esbuild";

esbuild.build({
 plugins: [subfont()],
}).catch(() => process.exit(1));

Webpack

In CommonJS form:

const SubfontWebpackPlugin = require("@ernxst/subfont/webpack");

module.exports = {
  plugins: [new SubfontWebpackPlugin()],
}

Configuration

  • log - Whether to log to stdout.
    • default: true

Contributing

To get started with development, you will need an editor (VS Code is recommended), a browser that runs JavaScript and some extra prerequisites:

To get started with contributing to this project, first fork this git repository:

git clone https://github.com/Ernxst/subfont.git

Then, install dependencies and start coding.

Submitting Improvements

If you have a suggestion that would make this app better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement".

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

Distributed under the MIT License. See LICENSE for more information.