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

@reliance/icons

v1.0.0

Published

Reliance UI React icon library

Downloads

486

Readme

@reliance/icons

React icon wrapper for the Reliance Design System. lucide-react is the primary library; @phosphor-icons/react is a fallback for glyphs lucide doesn't have.

Install

yarn add @reliance/icons

React 18 or 19.

Usage

Import the icon you want and hand the component to StaticIcon:

import { StaticIcon } from "@reliance/icons";
import { ChevronDown } from "@reliance/icons/lucide";

<StaticIcon icon={ChevronDown} size={20} />;

weight accepts Phosphor's vocabulary (thin, light, regular, bold, fill, duotone) and defaults to bold. lucide has no equivalent render mode, so weight maps to a strokeWidth, and fill/duotone additionally render the glyph solid.

Phosphor icons accept weight, color and size natively, so they need no wrapper — render them directly:

import { CaretDown } from "@reliance/icons/phosphor";

<CaretDown weight="fill" size={20} />;

Entry points

| Import | Contains | | ---------------------------- | ------------------------------------------------ | | @reliance/icons | StaticIcon, weight helpers, types, icons | | @reliance/icons/lucide | every lucide icon, as static named exports | | @reliance/icons/phosphor | every Phosphor icon, as static named exports | | @reliance/icons/dynamic | legacy <Icon name="…" />5.93 MB | | @reliance/icons/namespaces | legacy Icons / LucideLibraryIcons namespaces |

Why Icon moved to /dynamic

<Icon name="ChevronDown" /> looks up a string against the lucide and Phosphor namespaces at runtime. That means every glyph in both libraries has to exist in the bundle, so no bundler can tree-shake any of it. Measured cost of importing it: 5.93 MB raw / 1.31 MB gzip, versus ~4 KB raw / ~1.4 KB gzip for StaticIcon plus a static import.

This isn't a bundler configuration problem and no amount of sideEffects: false or subpath exports can fix it — it's inherent to resolving names at runtime. So it lives on its own entry, where paying for it is a deliberate choice. Reach for it only when the name genuinely isn't known until runtime (CMS- or API-driven content); for anything you can name in source, use StaticIcon.

scripts/check-bundle-size.mjs (yarn check-bundle-size) asserts the main entry never regains a dependency on either library — a single import * as or Object.keys() over a namespace is enough to put the 5.93 MB back, and nothing else would fail.

Regenerating

src/generated/ (the two barrels and the icons name list) is generated and committed. After bumping lucide-react or @phosphor-icons/react:

yarn generate-icons