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

@expo/styleguide-icons

v4.2.3

Published

Expo's icons for use on the web.

Vulnerabilities

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

Links

Git

Maintainers

ideidebrentvatnebrentvatneevanbaconevanbaconexpoadminexpoadminexponentexponentbycedricbycedrickudochienkudochienalanhughesalanhughestsapetatsapetaexpo-botexpo-botphilplphilplwschurmanwschurman

Keywords

Readme

@expo/styleguide-icons

Expo's icons for use on the web.

Getting started

  1. Install deps at the repo root: yarn.
  2. Copy .env.example to .env and set FIGMA_TOKEN to a personal access token (Figma → avatar → Settings → Security → Personal access tokens).
  3. Build: yarn build (from this package) or yarn build from the repo root.

Without a FIGMA_TOKEN the build falls back to an empty stub so downstream packages still compile.

Scripts

| Command | What it does | | --- | --- | | yarn build | Smart build. Checks Figma's lastModified; if unchanged, skips the API entirely and re-bundles the existing sources. | | yarn build-stub | Emits an empty package (no Figma, no icons). Used when FIGMA_TOKEN is missing. | | yarn refresh | Forces a Figma pull then rebuilds. Prints a timing breakdown (figmaExport / bundle / …). Available at the repo root too. |

Pipeline

One Node script — scripts/build.mjs — drives everything:

  1. Figma gate. Fetches the Figma file's lastModified and compares it to .figma-cache.json. Unchanged → skip export.
  2. Figma export. Runs @figma-export/core in-process with all four pages in parallel. figma-js's Client is wrapped in a Proxy that retries on HTTP 429 respecting Retry-After (Figma's recommendation). A live status line (TTY) collapses the per-icon progress; CI logs get per-page milestones only.
  3. Bundle. A single esbuild.build pass (bundle: false, minify, CJS, JSX automatic) transforms ~3,600 .tsx files straight into the final layout at the package root (custom/, duotone/, outline/, solid/, mergeClasses.js). No dist/ intermediate, no postbundle copy.
  4. Types. Every icon's .d.ts has an identical shape, so we template them instead of running tsc — near-instant.
  5. Incremental. An icon is skipped if its .js and .d.ts are both newer than the source .tsx.

Typical wall-times:

| Scenario | Time | | --- | --- | | No-op (Figma cached, outputs fresh) | ~0.5s | | Clean bundle (Figma cached, no output) | ~1.5s | | Force refresh (yarn refresh) | ~30–50s (Figma-bound; rate limit dependent) |

CI caches src/{custom,duotone,outline,solid} + .figma-cache.json separately, keyed only on Figma's lastModified, so every branch and PR reuses the same Figma snapshot — unrelated code pushes don't trigger a Figma refresh.