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

@buildingradar/icons_library

v0.0.1

Published

An icon library package for React applications

Readme

Br Icons Library

This library is a fork of 'lucide-react'

This library is used for implementation of the custom icons for react applications to be used in complementary with Lucide icons.

What is lucide? Read it here.

Installation

pnpm install @buildingradar/icons_library

How to use

First of all: make sure the icon conforms to the standards as described in docs/icon-design-guide.md, most importantly

  • Icons must be designed on a 24 by 24 pixels canvas.
  • For each icon these attributes are applied, corresponding to the above rules.
<svg
  xmlns="http://www.w3.org/2000/svg"
  width="24"
  height="24"
  viewBox="0 0 24 24"
  fill="none"
  stroke="currentColor"
  stroke-width="2"
  stroke-linecap="round"
  stroke-linejoin="round"
>
  <!-- SVGElements -->
</svg>
  • Allowed Elements SVG files may only contain simple path and shape elements, which may not have any attributes other than sizing and spacing.
    In practice only the following elements and attributes are allowed:
  • <path d>
  • <line x1 x2>
  • <polygon points>
  • <polyline points>
  • <circle cx cy r>
  • <ellipse cx cy rx ry>
  • <rect x y width height rx>

This also means that no transforms, filters, fills or explicit strokes are allowed.

Never use <use>. While it may sometimes seem like a good way to optimize file size, there's no way to ensure that the referenced element IDs will be unique once the SVGs are embedded in HTML documents.

In the ./icons directory, paste the svg file, and create a json file according to icon.schema.json. You can copy paste existing json of other icons and edit accordingly. The file name should be identical, in kebap-case. For example inbox-search.svg & inbox-search.json.

You should not modify anything else. Files in any other directory is forked from Lucide's repository.

The pnpm build command will auto generate TypeScript code and modules for icons. You don't need to do anything else.

Previews

Storybook is not implemented for this repository.

Steps to link this repo to other repo without publishing intermediate versions:

  • change the version number in package.json to a higher, temporary version. It helps for other repositories to recognize this is a different version and link correctly.
  • pnpm build to build,
  • npm link to create link for this repo
  • run npm link @buildingradar/icons_library in your repo using this lib
  • you can now import the new icons you added!

You can also publish test versions.

  • change the version number in package.json to a higher, temporary version. (e.g. 1.0.1-alpha.1)
  • npm publish
  • use it in your repo