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

@paradox-design/icon-set

v0.1.0

Published

Default icon set for Paradox Design System

Readme

@paradox-design/icon-set

The default icon set of Paradox Design System.

You do not install or import this package yourself — @paradox-design/icons depends on it, and <pdx-icon> uses it out of the box. A client with their own icons replaces it entirely with setIconSet() (see @paradox-design/icons); thanks to lazy loading, none of our icons are downloaded then.

What is inside

import { iconNames, loaders } from '@paradox-design/icon-set';

| Export | Description | | ----------- | ------------------------------------------------------------- | | iconNames | sorted list of icon names | | loaders | name → () => Promise<svg> — one dynamic import() per icon | | IconName | union type of all names |

The gallery of all icons is in Storybook: Components/Icon → Zestaw domyslny.

Names are ours

Icon names describe meaning, not shape: close, warning, success, trash. The upstream name (e.g. Lucide x, triangle-alert) is recorded in sources.json. Changing how warning looks never breaks the components that use it.

Adding an icon

  1. Put svg/<name>.svg in the package — drawn by hand or copied from a source with an allowed license. Name: lowercase words joined by -.

  2. Add an entry to sources.json:

    "name": { "source": "lucide", "upstream": "original-name" }

    An icon of our own uses "source": "paradox" (declare that source once).

  3. pnpm --filter @paradox-design/icon-set build.

The build fails when:

  • an SVG has no sources.json entry, or an entry has no SVG;
  • a source's license is not in allowedLicenses (MIT, ISC, CC0-1.0), or its notice file is missing;
  • the SVG contains a script, styles, foreignObject, a DTD, an on* handler, href, or a hard-coded color instead of currentColor;
  • viewBox is not 0 0 24 24.

The build cannot use the sanitizer from @paradox-design/icons — icons depends on this package, so the reverse dependency would create a cycle. Validation here is structural and deliberately stricter: a doubtful icon is rejected, not repaired.

Licenses

The package code is MIT. Icons taken from Lucide are ISC (Feather-derived ones also MIT); the full notice ships in licenses/lucide.txt. Icons drawn by Paradox are covered by the package license.

License

MIT © Paradox Software