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

vite-plugin-svg-spritegen

v2.0.7

Published

Vite plugin that generates an svg spritesheet, optionally removing unused svg files.

Downloads

924

Readme

npm GitHub npm

vite-plugin-svg-spritegen

Installation

v2.x is Vite 8+ only. Use v1.x for Vite 5-7

npm install -D vite-plugin-svg-spritegen

Usage

// vite.config.js
import { svgSpritegen } from 'vite-plugin-svg-spritegen';

export default {
  plugins: [
    svgSpritegen({
      input: [
        {
          baseDir: 'src/assets/icons',
        },
        {
          baseDir: 'node_modules/lucide-static/icons',
          removeAttrs: ['class', 'stroke-width', 'stroke-linecap', 'stroke-linejoin'],
        },
      ],
      outputDir: 'src/assets/icons',
    }),
  ],
};

Generated Files

The plugin writes two files to outputDir:

  • sprite.svg — the generated spritesheet. This is a build artifact, so the plugin adds it to a .gitignore inside outputDir (disable this with gitignore: false).
  • types.ts — the IconName type and iconNames array, always generated from the full set of source SVGs (stripUnused never affects it). Commit this file so typechecking works on a fresh clone without running a build first. It regenerates automatically on every dev-server start and build, so it can't drift for long.

Upgrading from v2.0.1 or earlier? Previous versions added types.ts to the generated .gitignore. The plugin removes that stale entry the next time it runs — after that, git add your types.ts to start tracking it.

Example Icon Component

import spriteHref from '~/assets/icons/sprite.svg';
import type { FC, SVGProps } from 'react';
import type { IconName } from '~/assets/icons/types';

export const IconBase: FC<SVGProps<SVGSVGElement> & { icon: IconName }> = ({ icon, ...props }) => {
    return (
        <svg {...props}>
            <use href={`${spriteHref}#${icon}`} />
        </svg>
    );
};

Usage Example

<Icon icon="plus" />

Stripping Unused Icons

By default the plugin scans your source files during build and drops any icons that aren't referenced, keeping the emitted sprite.svg small. Configure this via stripUnused:

svgSpritegen({
  outputDir: 'src/assets/icons',
  stripUnused: {
    // Set false to include every source SVG in the sprite.
    enabled: true,
    // A RegExp (or string) with a named capture group `icon`. Every match is checked
    // against the real icon set, so unrelated strings are ignored automatically.
    matchPattern: /['"`](?<icon>[^'"`\r\n]+?)['"`]/g,
    // Which files to scan / skip (node_modules is always excluded). These are matched by
    // rolldown's native glob engine, which supports `*`, `**`, and `[...]` character classes
    // but NOT extglobs like `?(x)`, `@(a|b)`, `+(...)` — list each extension explicitly.
    srcInclude: [
      '**/*.js', '**/*.jsx', '**/*.ts', '**/*.tsx',
      '**/*.mjs', '**/*.cjs', '**/*.mts', '**/*.cts',
      '**/*.md', '**/*.mdx',
    ],
    srcExclude: [],
    // Icon ids to always keep, even if they aren't detected in source.
    whitelist: [],
  },
});

The default matchPattern treats any quoted string ("star", 'star', or `star`) as a possible icon reference. Because each candidate is validated against the generated icon set before being kept, over-matching is harmless — this catches icon names wherever they appear (component props, object/record values, ternaries, arrays) rather than only icon="..." assignments. Provide your own matchPattern (with an icon named group) to narrow this if needed, and use whitelist for icons chosen in ways static analysis can't see (e.g. names built from runtime data).