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

@rei/cedar-icons

v2.6.1

Published

REI Cedar Icon Library

Downloads

33

Readme

icons

Summary

@rei/cedar-icons is home to the raw svg files that conform to REI's Iconography guidelines

Getting Started

There are 2 primary ways of consuming Cedar Icons:

Using a sprite sheet ensures that each icon used on your page is only included once. However this does create an additional maintenance cost as you must track exactly which icons are being used inside of your application, and adding a new icon to the page means generating a new sprite sheet.

Using inline icon components is the easiest way to consume Cedar Icons, as it ensures that the icon content is always available where it needs to be. However it does mean that some icons might be included multiple times in your bundle, especially if you are doing server-side rendering.

Which approach you take will depend on the needs of your project. Feel free to reach out to the Cedar team for help in assessing the best strategy for you.

Creating a custom sprite

See the CdrIcon docs for more information on how to reference and load your sprite sheet in your application.

Via CLI

@rei/cedar-icons provides a command-line interface for creating/editing a SVG symbol definition file.

npx icon-sprite will start the CLI. Follow the instructions to create your customized sprite.

NOTE: If you are editing an existing sprite via the CLI it will only look for icons currently in the repo and anything not found within will be excluded from the output file (this may change with a future feature update).

From within the repo

npm run sprite will function the same as above.

Using Icons Inline

To make it easier for consumers to inline individual icons we export single component versions of every SVG icon in this library from @rei/cedar. See the CdrIcon docs for more information.

Programmatic Usage

npm install @rei/cedar-icons

Distributed Files

  • all-icons.svg: SVG sprite sheet containing all of the icons.
  • icons.esm.js: ESM export of SVG markup. Exports are formatted in CamelCase: CaretDown
  • icons.js: CJS export of SVG markup. Icon names are formatted in kebab-case: caret-down
  • icons.json: JSON object. Icon names formatted in kebab-case: caret-down
  • /icons/: folder of .svg files. Filenames formatted in kebab-case: caret-down.svg

Use

@rei/cedar-icons exposes an object that has the following structure:

{
  <icon-name>: <SVG String>
}

for example:

{
  camping: "<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24">...</svg>"
}

SVGs

Source svg files are found in icons/

"Docs" view

Compiles and hot-reloads for development

npm run serve

Compiles and minifies for production

npm run build

Development

Assets added to this repo should conform to the CdrIcon guidelines. Before adding a new icon to this repo, first run the optimization script:

node build/svgo.js PATH_TO_NEW_ICON.svg

This script will run the icon data through SVGO to reduce it's file size, then copy it into the /icons directory.