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

@xola/icons

v1.1.33

Published

Xola's icon set

Readme

@xola/icons

Xola's icon set. Each icon is a typed React component, written in TypeScript.

Table of Contents

Installation

Run this command in your project.

npm install @xola/icons

The package requires these versions.

  • Node.js v16 or higher
  • NPM v7 or higher
  • React 17, 18, or 19 (peer dependency)

Usage

Import an icon and render it like any other component.

import { AccountIcon } from "@xola/icons";

const Example = () => <AccountIcon className="text-primary" />;

Each icon accepts standard SVG props (className, fill, onClick, and so on) plus a size prop.

<AccountIcon size="large" />

Browse the full icon set in Storybook at ui.xola.io.

Configuration

The size prop accepts one of four values. Each value maps to a fixed Tailwind width/height class.

| Size | Class | Pixels | | -------- | ------------- | ------ | | tiny | w-3 h-3 | 12px | | small | w-3.5 h-3.5 | 14px | | medium | w-4.5 h-4.5 | 18px | | large | w-6 h-6 | 24px |

size defaults to small when you omit it. The IconSize type (plus IconProps/IconComponent) is exported from the package root if you need to type a prop that accepts it.

import type { IconSize } from "@xola/icons";

The package ships as TypeScript source with no build step (main/types point at ./index.ts). Your bundler compiles the icon files directly, so you get typed props without a separate @types package. This also means consumers type-check this package's raw source under their own tsconfig.json, not a pre-built .d.ts.

Every .tsx file that uses JSX must start with import React from "react";, even though the automatic JSX runtime doesn't require it. Consumer apps using the classic JSX runtime ("jsx": "react") need React in scope per-file, and since this package ships raw source, their tsconfig applies, not ours. Missing this import surfaces as TS2686: 'React' refers to a UMD global, but the current file is a module in the consuming app, not here, so it's easy to miss. Run npm run typecheck after adding an icon, but also grep for it directly since this repo's own tsconfig may not catch it:

grep -rL "^import React" src --include="*.tsx" | grep -v helpers/

Development

Run these commands from the src/icons/ folder.

npm install
npm run lint
npm run typecheck
npm run format

npm run lint runs ESLint with autofix. npm run typecheck runs tsc --noEmit. npm run format runs Prettier.

Publish

Follow these steps in the src/icons/ folder to publish a new version.

  1. Bump the version number.

    npm version <your-new-version>
  2. Publish the package.

    npm publish --tag=latest
  3. Confirm the new version on the npm package page.