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

@verbb/plugin-kit-icons

v2.0.22

Published

Curated UI icons as **raw SVG path data** — no icon font, no external icon runtime. Each glyph is `{ width, height, path }`, so bundlers only ship the icons you import.

Readme

@verbb/plugin-kit-icons

Curated UI icons as raw SVG path data — no icon font, no external icon runtime. Each glyph is { width, height, path }, so bundlers only ship the icons you import.

Used by @verbb/plugin-kit-web (<pk-icon>) and the React/Vue <Icon> facades.

Install

npm install @verbb/plugin-kit-icons

Register for <pk-icon> / <Icon>

The name registry starts empty in bundler builds. Register the glyphs your markup looks up.

On Craft CP pages that load several Plugin Kit plugins, each Vite bundle includes its own copy of this package. Registrations still merge into one page-global map (globalThis), so Plugin B’s registerIcons({ gear }) is visible to Plugin A’s winning <pk-icon>.

import '@verbb/plugin-kit-web/components/icon.js';
import { registerIcons, plus, gear, ellipsis } from '@verbb/plugin-kit-icons';

registerIcons({ plus, gear, ellipsis });
<pk-icon icon="plus"></pk-icon>
<pk-icon icon="gear" label="Settings"></pk-icon>

<pk-button>
  <pk-icon icon="plus" slot="start"></pk-icon>
  Add
</pk-button>

Full curated set in one shot (larger bundle):

import '@verbb/plugin-kit-icons/all.js';

The no-build Plugin Kit loader already includes that full set.

Sizing & colour

Icons follow font-size (default 1em) and currentColor:

<pk-icon icon="trash" style="font-size: 18px; color: #b91c1c"></pk-icon>

Accessibility

Pass label="…" when the icon is meaningful on its own (image + title). Omit it for decorative icons — they are hidden from assistive tech.

Use path data in JS

Tree-shakeable named exports — no registry required:

import { chevronDown, iconToSvg } from '@verbb/plugin-kit-icons';

element.innerHTML = iconToSvg(chevronDown);
element.innerHTML = iconToSvg(chevronDown, { title: 'Expand' });

Or register a name, then render <pk-icon>:

import { registerIcon, chevronDown } from '@verbb/plugin-kit-icons';

registerIcon('chevron-down', chevronDown);
element.innerHTML = `<pk-icon icon="chevron-down"></pk-icon>`;

React / Vue

Facades resolve the same registry. Register glyphs (or import all.js) before the first string lookup:

import { registerIcons, plus } from '@verbb/plugin-kit-icons';
import { Icon, Button } from '@verbb/plugin-kit-react/components';

registerIcons({ plus });

<Icon icon="plus" className="size-4" />
<Icon icon="plus" label="Add" />

<Button>
  <Icon slot="start" icon="plus" />
  Add
</Button>
<script setup>
import { registerIcons, plus } from '@verbb/plugin-kit-icons';
import { Icon, Button } from '@verbb/plugin-kit-vue/components';

registerIcons({ plus });
</script>

<template>
  <Button>
    <Icon slot="start" icon="plus" />
    Add
  </Button>
</template>

Naming

Use one kebab-case name per glyph in HTML / the registry, and the matching camelCase export in JS. Prefer the curated names as shipped — do not invent kit-local synonyms (search, add, plus-circle); use magnifying-glass, plus, circle-plus, and so on.

| Context | Form | Example | |---------|------|---------| | HTML / getIcon | kebab-case | chevron-down, arrow-up, arrows-rotate | | JS exports | camelCase | chevronDown, arrowUp, arrowsRotate |

registerIcons({ arrowUp }) stores under arrow-up for HTML lookup. Prefer arrows-rotate for reload controls over arrow-rotate-left / arrow-rotate-right.

ViewBox / canvas

Glyphs are stored edge-cropped (variable width × canvas height, usually 512). At render time, iconViewBox() expands that to a centered square so every icon fills <pk-icon>’s square 1em host evenly, without rewriting path data. Rendered SVGs also set overflow="visible" so intentional canvas overhang is not clipped.

The full curated set is documented on the Icon component Gallery under Web / React / Vue.

import { getIcon, getIconNames } from '@verbb/plugin-kit-icons';

getIcon('gear');     // PkIcon | undefined (after register)
getIconNames();      // registered kebab-case names

App-specific icons

Icons that should not join the shared set can still use the same lookup path:

import { registerIcon, registerIcons } from '@verbb/plugin-kit-icons';

registerIcon('sliders', {
  width: 512,
  height: 512,
  path: 'M32 64…',
});

registerIcons({
  'my-widget': { width: 512, height: 512, path: '…' },
});

Register before the first render that looks up those names.