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

favgen

v0.2.7

Published

CLI tool to generate a set of favicons from a single input file.

Readme

npm

This is a simple CLI tool to generate an optimized set of favicons from a single input file. Icons are optimized in terms of both size and quantity (nowadays you don't need that many of them). They are produced according to this article which served as an inspiration for the tool.

CLI usage

Use it like this: npx favgen /path/to/input -o /path/to/output.

You can tweak the following settings by giving additional commands:

  • output directory by providing -o option with a path (__favicons__ by default)
  • colors palette size by providing --colors with a number between 2 and 256 (64 by default)

Input file can be in any of the following formats: JPEG, PNG, WebP, GIF, AVIF, TIFF or SVG (anything sharp library accepts).

By default, the following set of favicons is produced:

  • icon.svg (only if input file is SVG)
  • favicon.ico 32x32
  • icon-192.png 192x192 (for Android devices)
  • icon-512.png 512x512 (for Android devices)
  • icon-mask.png 512x512 with safe padding (for Android maskable icon support)
  • apple-touch-icon.png 180x180 (original image is resized to 140x140 and 20px transparent padding is added on each side; rationale for this is given in the article)

Additionally, a sample manifest.webmanifest file is produced which includes regular and maskable Android icons.

Besides that, PNG output is optimized by sharp (which uses pngquant) and SVG output is optimized by SVGO. Also, color palette is reduced to 64 colors by default in order to reduce assets’ size.

JS API usage

The tool can be also used as API:

const { produceIcons } = require("favgen")
const inputFilePath = "icon.svg"
const outputDirPath = "__favicons__"
const paletteSize = 64 // default value
produceIcons(inputFilePath, outputDirPath, paletteSize)

Vite plugin usage

Install:

npm i favgen

Configure in vite.config.js or vite.config.ts:

import { defineConfig } from "vite"
import { favgenVitePlugin } from "favgen"

export default defineConfig({
  plugins: [
    favgenVitePlugin({
      source: "src/assets/logo.svg",
      colors: 64,
      assetsPath: "favicons",
    }),
  ],
})

Vite plugin options:

  • source (required): path to source image (SVG, PNG, JPEG, WebP, GIF, AVIF, TIFF)
  • colors (optional): PNG palette size between 2 and 256 (64 by default)
  • assetsPath (optional): subdirectory where generated assets are emitted (e.g. favicons)

The plugin runs on build and:

  • generates favicon assets using the same logic as CLI/API
  • emits them into the final build output
  • injects links into built HTML:
    • favicon.ico
    • icon.svg (only when source is SVG)
    • apple-touch-icon.png
    • manifest.webmanifest

Generated files:

  • icon.svg (only for SVG source)
  • favicon.ico
  • icon-192.png
  • icon-512.png
  • icon-mask.png
  • apple-touch-icon.png
  • manifest.webmanifest

Manifest icon URLs and injected HTML links are automatically adjusted for Vite base and assetsPath settings.

Webpack plugin usage

Install:

npm i favgen

Configure in your webpack config:

const FavgenWebpackPlugin = require("favgen").FavgenWebpackPlugin

module.exports = {
  // ...rest of config
  plugins: [
    new FavgenWebpackPlugin({
      source: "src/assets/logo.svg",
      colors: 64,
      assetsPath: "favicons",
    }),
  ],
}

Webpack plugin options:

  • source (required): path to source image (SVG, PNG, JPEG, WebP, GIF, AVIF, TIFF)
  • colors (optional): PNG palette size between 2 and 256 (64 by default)
  • assetsPath (optional): subdirectory where generated assets are emitted (e.g. favicons)

The plugin runs during webpack compilation and:

  • generates favicon assets using the same logic as CLI/API
  • emits assets into compilation output
  • injects links into generated .html assets:
    • favicon.ico
    • icon.svg (only when source is SVG)
    • apple-touch-icon.png
    • manifest.webmanifest

Manifest icon URLs and injected HTML links are automatically adjusted for webpack output.publicPath and assetsPath.