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 🙏

© 2025 – Pkg Stats / Ryan Hefner

gfont-loader

v1.3.2

Published

How Google Fonts Loading in JS Should Be

Readme


Usage

Install this package in your project:

# via npm
npm add gfont-loader

# or pnpm
pnpm add gfont-loader

# or yarn
yarn add gfont-loader

To load fonts, call loadGFont():

// demo.ts
import { loadGFont } from "gfont-loader";

// single family with default axis
await loadGFont("Montserrat");

// single family with specific axis
await loadGFont({
  family: "Montserrat",
  axis: {
    // ital?: italic, e.g. 0, 1
    // wdth?: width, e.g. 75, "80..100"
    // wght?: weight, e.g. 300, "200..800"

    // [axis]: any other axis available

    // most axis allow <value> | <range>
    // <value>: number | numeric string
    // <range>: `<value>..<value>`
  }
});

// single family with multiple axis
await loadGFont({
  family: "Montserrat",
  axis: [...] // same format as above (number of axis specified must match)
});

// multiple families
await loadGFont([...]); // same format as above (mixable) in array

// only for specific characters
await loadGFont(..., {
  text: "Hello World!" // spaces etc. would be auto encoded i.e. %20
});

// use loading strategy other than "swap"
await loadGFont(..., {
  strat: "optional" // "auto" | "block" | "swap" | "fallback" | "optional"
});

If there's no reasons to wait for the font to resolve, use void loadGFont(...) instead of await loadGFont(...).

FAQ

Q: Why not just use CSS @import etc. directly?

A: This is for package developers that want to load fonts via J/TS, not for web developers.

Q: Why not just use the (sort of) official webfontloader?

A: That's from 8 years ago and hella obsolete. It's also way larger and could hardly be tree-shaked even if you're only importing from Google Fonts.
(i.e. 13kB vs <1kB for CJS build)


 How could such packages not be updated for over 8 years...?