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

@smartyweb/ui

v1.5.0

Published

Shared React component library consumed by multiple Next.js microservices via private npm.

Readme

@smartyweb/ui

Shared React component library consumed by multiple Next.js microservices via private npm.

Installation

npm install @smartyweb/ui

Requires React 19 (a peer dependency). Import the stylesheet once in your app's entry point, then import components:

import "@smartyweb/ui/styles.css";
import { H1, Button } from "@smartyweb/ui";

Font Setup

This library does not bundle fonts. Consumers load fonts and expose them as CSS custom properties. The library reads these three variables:

| CSS variable | Font | Used by | | ------------------- | ------------ | --------------------------------- | | --ui-font-primary | TT Hoves Pro | All heading and button components | | --ui-font-body | Inter | Body and paragraph components | | --ui-font-code | Hack | Code component |

In a Next.js app using next/font/local, set these on the root element:

// app/layout.tsx
import localFont from "next/font/local";

const ttHovesPro = localFont({
  src: [...],
  variable: "--font-tthoves",
});

export default function RootLayout({ children }) {
  return (
    <html className={ttHovesPro.variable}>
      <body
        style={{
          "--ui-font-primary": "var(--font-tthoves, 'TT Hoves Pro', system-ui, sans-serif)",
        }}
      >
        {children}
      </body>
    </html>
  );
}

If a variable is not set, components fall back to system-ui (headings/body) or monospace (code).

Developing this library

This is a skills-driven codebase — for any repeatable task, reach for a skill (or author one) rather than doing it by hand. Skills are verified, step-by-step walkthroughs that encode our process; run one by typing its slash command in Claude Code.

| Skill | What it does | | ------------------ | -------------------------------------------------------------------------------------- | | /validate-tokens | Validate a Tokens Studio sync end-to-end — drift, math, Figma source-of-truth. | | /version-up | Cut a new version with changesets (bump, changelog, release prep). | | /commit-push | Commit and push all changes with a summary commit message. | | /link-ui | Live-link local @smartyweb/ui into storefront-2 so edits show up without publishing. |

Local commands, for the times you do need to run something by hand:

npm install         # install dependencies
npm run storybook   # generate tokens, then run Storybook (component workbench)
npm run build       # generate tokens, then build to dist/
npm run tokens      # regenerate src/styles/generated/*.generated.scss from tokens.json

For how the codebase is laid out and why it's built this way, see CLAUDE.md, docs/PRINCIPLES.md, and the decision records in docs/adr/.