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

@armor/icons

v1.8.0

Published

Webfont icons for Armor web applications.

Readme

Build Status @armor/api Managed With

@armor/icons

Webfont icons for Armor web applications.

Prerequisites

Installation

All dependencies are installed with NPM by running npm install.

Usage

This package is included as a dependency of Brandkit. In most cases applications that will use this package, will also use Brandkit. If you only need to use the icons, directly install the @armor/icons package:

npm install --save-dev @armor/icons

Then reference the icons in your project's Sass file:

@import "../../node_modules/@armor/icons/src/icons-core";
@import "../../node_modules/@armor/icons/src/icons-infrastructure";
@import "../../node_modules/@armor/icons/src/icons-security";

Icons in Markup

To include an icon in markup, add the .ico class for the specific icon you want to add.

<i class="ico ico-armor"></i>

It is possible to use other elements besides <i>, however we strongly recommend standardizing on the use of this element because it is deprecated in HTML5 and unused elsewhere throughout our standard codebase.

Icons in Sass

You can add icons to custom classes by either using the @extend syntax of Sass:

.my-custom-class {
  @extend .ico;
  @extend .ico-armor;
}

You can also use the bare components to construct a custom class:

.my-custom-class {
  &::after {
    font-family: 'icons-core';
    display: block;
  }

  &.complete::after {
    content: $ico-enable;
    color: $green-700;
  }

  &.error::after {
    content: $ico-exclamation-triangle;
    color: $red-700;
  }
}

Development

Compilation of the webfont uses Gulp. You can trigger a Gulp build by running npm run build. This will compile the webfont from the source SVG images.

Adding New Icons

To add an additional icon, simply add the SVG image to the module directory of the module to which you want to add the icon. The image name will be used as the CSS class name, so the filename should follow our CSS class naming convention (e.g. kebab-case-image.svg). Once you've added the new SVG, run npm run build again to make sure that it compiles correctly.

Compilation re-generates and rewrites the HTML, SCSS, and CSS source files. Commit these files (including newly-added SVG files) back to source control.

Note: Be sure to check for alignment regressions after new builds.

Adding New Modules

Modules are separate SCSS/CSS payloads that allow a user of the package to import only subsets of icons that they need without having to facilitate CSS tree-shaking in their project.

To add a module, add a new directory in src/icons. Similarly to image names, the module names should also follow our naming convention (kebab-case). You'll also need to add the new module to config.json in the root of the project.