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

my-icon-lib

v0.0.3

Published

Angular icon library providing a simple <lib-icon> component backed by SVG icon data.

Readme

my-icon-lib

Angular icon library providing a simple <lib-icon> component backed by SVG icon data.

This package is designed to be lightweight and easy to drop into any Angular application. It exposes a single icon component that renders inline SVGs from a predefined icon set.


Installation

Install from npm:

npm install my-icon-lib

Make sure your Angular version is compatible with the peer dependencies declared in the package (@angular/core and @angular/common).


Usage

1. Standalone component usage

If you are using standalone components in Angular, import the icon component directly:

import { Component } from '@angular/core';
import { MyIconComponent } from 'my-icon-lib';

@Component({
  selector: 'app-root',
  standalone: true,
  imports: [MyIconComponent],
  template: `
    <!-- Icon by name -->
    <lib-icon name="home"></lib-icon>

    <!-- Attribute-style usage -->
    <lib-icon filter></lib-icon>
    <lib-icon search></lib-icon>
  `,
})
export class AppComponent {}

2. NgModule usage

If you are using NgModules, import the library module and use the <lib-icon> component in your templates:

import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { AppComponent } from './app.component';
import { MyIconLibModule } from 'my-icon-lib';

@NgModule({
  declarations: [AppComponent],
  imports: [BrowserModule, MyIconLibModule],
  bootstrap: [AppComponent],
})
export class AppModule {}

Then in your component template:

<lib-icon name="home"></lib-icon>
<lib-icon menu></lib-icon>
<lib-icon settings></lib-icon>

Available icons

The library ships with a predefined set of SVG icons. You can reference them either via the name input or via attribute-style inputs. Common examples include:

  • home
  • menu
  • search
  • settings
  • user
  • filter
  • report
  • email

Additional icons are available and defined internally in the MY_ICONS map.


Development

To build the library from source:

ng build my-icon-lib

This will emit the compiled package to dist/my-icon-lib.

To run unit tests:

ng test

Publishing

After building the library, you can publish it to the npm registry:

ng build my-icon-lib
cd dist/my-icon-lib
npm publish

Ensure that your package.json is correctly configured (name, version, description, author, license, and keywords) and that you are logged in to npm with an account that has permission to publish the chosen package name.