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

@odoro-cli/icons

v2.0.0

Published

Odoro icon module: several packs normalised on one contract, one export per icon so that tree shaking works.

Readme

@odoro-cli/icons

Five icon packs for Odoro, imported one at a time.

npm i @odoro-cli/icons
import { Icon } from '@odoro-cli/icons'
import { ArrowRight, Sparkles } from '@odoro-cli/icons/outline'

;<Icon of={ArrowRight} className="o-size-5" />

The packs

| Entry point | Style | Count | | --------------------------- | ------------- | ----: | | @odoro-cli/icons/outline | Outline | 2048 | | @odoro-cli/icons/compact | Compact solid | 2078 | | @odoro-cli/icons/classic | Classic | 2001 | | @odoro-cli/icons/extended | Extended | 3903 | | @odoro-cli/icons/brands | Brand marks | 609 |

@odoro-cli/icons/catalogue.json lists every name, if you need to build a picker.

You ship what you import

Each icon is a separate export, so a bundler keeps only the ones your code names. Importing from a pack does not pull the pack in.

That is also why the packs are separate entry points rather than one big index: a single barrel would make every icon reachable from one import, and tree-shaking would have far more work to prove what can go.

Colour and size come from the outside

Icons are drawn with currentColor and sized by their container. They take the colour of the text around them, in light and dark alike, with nothing to configure.

<span className="o-text-brand-500">
  <Icon of={Sparkles} className="o-size-6" />
</span>

Links

Licence

UNLICENSED. Copyright (c) BouBouw. See LICENSE. Icon sources and their own licences are listed in CREDITS.md at the root of the repository.