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

gantri-components

v2.209.0

Published

1. From [Figma](https://www.figma.com/file/7XptZJEfgLsGIjLT4PAFXY/Gantri-DS-%7C-Atoms?node-id=1%3A9456&t=BvL578PsHUyfuJYh-1), right click on icon from sidebar (Make sure you have the right element selected. They should be 16x16 or 24x24) and click `Copy/P

Downloads

2,613

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

gantrigantri

Keywords

Readme

ui-library

Adding new icons

  1. From Figma, right click on icon from sidebar (Make sure you have the right element selected. They should be 16x16 or 24x24) and click Copy/Paste as > Copy as SVG.
  2. Create a new .svg file in the /src/assets/icons/__APPROPRIATE_CATEGORY_FOLDER__/ directory with the same name as what appears in Figma minus ic_ and _16 (example: ic_corner_16 and ic_corner_24 become corner and corner_24).
  3. Look at each new svg file and verify that the viewbox is viewbox="0 0 16 16" or viewbox="0 0 24 24", as applicable. Update any that are not the appropriate value. If the icons do not look correct when complete, you can try reverting the change or talk to the designers about correcting them.
  4. Update fill attributes to reference value "currentColor". stroke attributes should also be updated. Be careful to check that the updated icon matches the original icon. Send the icon back to the designers to correct if there are any issues.
  5. Remove IDs and masks. Be careful to check that the updated icon matches the original icon. Send the icon back to the designers to correct if there are any issues.
  6. Run yarn run generate-icons
  7. Check for references to .ds_store and delete them, if present.

Deploying beta code changes

If you'd like to deploy some code that can be pulled into another repo, you can merge your changes into the beta branch. After deployment (you can verify deployment status here), you can install the beta code to your repo using yarn add gantri-components@beta. Just be sure not to reinstall the normal version when you're done.

NOTE: chore commit prefixes do not trigger a new version deployment. For a list of commit prefixes and their deployment versions, please see this document.

Testing

Testing is done using Jest for base JavaScript functionality and Jest with React Testing Library for React functionality.

You can run all tests locally by running yarn test in the command line. By default, this script is run with the --watch option which will watch for saved changes and automatically re-run related tests. You can add other options to the command by adding running yarn test {{option flag}} (example: yarn test --verbose).

All tests are run on GitHub each time new code is pushed to your PR.