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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@clearkit/icons

v2.112.2-alpha.0

Published

A directory of ClearKit glyph icons for consumption by the ClearKit React component library.

Downloads

1,421

Readme

ClearKit Icon Packages

Icons for consumption by applications that implement ClearKit.

Adding new icons

  1. Icons are created in the ClearKit Figma library and exported as SVGs. The design team is responsible for this process.
  2. Once developer has prepared SVG files from design, then add the SVG file(s) to correct directory inside /packages/icons/icons/* most icons should be added to /glyphs, unless it is a Nav, Service, or Identity icon.
  3. Run yarn setup and yarn start:docs to verify that icon displays properly
  4. Create a pull request and label with "minor" label
  5. Once CI passes, share the Netlify preview link with designer to verify that the icon meets expectations

Glyphs

  • Created on an 18x18 grid
  • Paths should be flattened (unless the glyph should support multi-path)
  • Any fill on exported paths will be stripped in the build process

Multi-path glyphs

Certain glyphs that require multiple fills e.g. an icon with a badge or foreground element, can be exported with multiple paths. When this is done the exported <path> elements should be given class names so they can be targeted in CSS.

Give each <path> a class attribute as follows -

  • Assign base to the path that makes up the base of the glyph
  • Assign modifier to the path that is intended to take a different fill

By default, all path elements will still receive fill="currentColor" so can still be rendered with a single color.

Nav

  • Created on a 22x22 grid
  • Paths should be flattened
  • Any fill on exported paths will be stripped in the build process

Services

  • Created on a 26x26 grid
  • Icons should be exported with their intended fills
  • All fill attributes will be preserved in the build process

Identity

  • Created on a 72x72 grid
  • Icons should be exported with their intended fills
  • All fill attributes will be preserved in the build process