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

@gladysassistant/theme-optimized

v2.1.0

Published

Theme optimized

Readme

@gladysassistant/theme-optimized

Optimized Tabler-based theme for Gladys Assistant, published as a single dashboard.css plus the icon webfonts it references.

Releasing

Releases are driven by the Release workflow (.github/workflows/release.yml), launched manually from the Actions tab.

Pick a bump:

  • none — publish the version already in package.json as-is (no commit)
  • patch / minor / major — bump package.json, commit it, then publish

The workflow then tags vX.Y.Z, pushes the commit and the tag to the branch it was run from, publishes to npm and creates a GitHub release with generated notes. Tick dry_run to rehearse everything without pushing or publishing.

A release is four separate publications — commit, tag, npm, GitHub release — so a run that dies halfway leaves some of them done. Re-running with none picks up where it stopped: it reuses the existing tag and skips whatever already landed, rather than refusing to start. A bump other than none still refuses to run if its tag or npm version already exists, since that means the bump collides with a finished release.

Publishing goes through npm trusted publishing (OIDC), so there is no NPM_TOKEN secret to maintain. npm authenticates the workflow itself, which means the trusted publisher configured on npmjs.com must point at this repository and at the workflow file name release.yml — renaming that file breaks publishing until the npm side is updated. Provenance attestations are generated automatically for OIDC publishes.

Icon font

Since v2.0.0, the fe fe-* icon classes are backed by Lucide (the actively maintained fork of Feather Icons) instead of the original Feather webfont. Class names are unchanged, so no change is required in consuming code.

Two fonts are shipped:

  • fonts/lucide/lucide-webfont.* — Lucide glyphs, subsetted to the icons listed in scripts/icon-names.json
  • fonts/feather/feather-brands.* — the 10 brand icons (github, twitter, slack…) that Lucide removed in 2022, kept from the original Feather font for backward compatibility

fonts/feather/feather-webfont.ttf is no longer referenced by the CSS but is kept as the source the brand glyphs are extracted from.

Adding or updating icons

  1. Add the icon name (any name from lucide.dev/icons) to the lucide list in scripts/icon-names.json.
  2. Regenerate the fonts and the CSS icon block:
npm pack lucide-static && mkdir -p lucide-static && tar xzf lucide-static-*.tgz -C lucide-static
pip install fonttools brotli
python3 scripts/generate-icon-font.py --lucide-dir lucide-static/package

The script subsets the Lucide webfont, regenerates the .fe-* rules at the end of dashboard.css, and keeps the brand-icon companion font in sync.