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

@tactics/storybook-icons

v0.1.1

Published

Icon library for the Tactics product suite (Core + Loket)

Readme

@tactics/storybook-icons

Icon library for the Tactics product suite, shared across apps instead of each maintaining its own copy.

Structure

Two top-level namespaces, each split by asset kind:

  • core — BackOffice/FrontOffice (the "sporting" product). Not yet migrated — these subpaths currently export nothing and exist only so consumers can start depending on them ahead of that migration.
  • loket — the Lokaal Loket childcare product (this repo's original source, extracted from @tactics/lokaal-loket).

Each namespace exposes icon, figure, and decoration subpaths:

@tactics/storybook-icons/loket/icon
@tactics/storybook-icons/loket/figure
@tactics/storybook-icons/loket/decoration
@tactics/storybook-icons/core/icon
@tactics/storybook-icons/core/figure
@tactics/storybook-icons/core/decoration

Import from the specific subpath you need — not the root package — so bundlers only pull in what's used.

Theming

Every component takes its color(s) as an explicit prop (theme/color) — there is no context provider and no dependency on any app's design-system package. Callers own theme resolution and pass a plain value in:

import {Icon, IconType} from "@tactics/storybook-icons/loket/icon";

<Icon type={IconType.SEARCH} theme={{stroke: "#111111"}} />;

Development

pnpm install
pnpm run storybook   # local dev
pnpm run build       # typecheck + tsup build
pnpm run build:storybook

Releasing: bump version in package.json on main. CI tags the commit, then builds from source and publishes to npm — nothing is committed to git under build/ or storybook-static/.