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

@cityofportland/components-react

v1.0.0-alpha.6

Published

Portland Component Library using design tokens from Figma

Readme

@cityofportland/components-react

The React implementation of the design system. Vite builds each component as its own ES module with matching TypeScript declarations and CSS, so you only ship what you actually import.

Under the hood it's built on @cityofportland/design-tokens for values, @cityofportland/components-css for styling, and @cityofportland/types for shared prop contracts — so it stays in sync with the Lit and Drupal versions of the same components.

Using it

pnpm add @cityofportland/components-react

React and React DOM are peer dependencies, so make sure your app already has those installed. Import components one at a time to keep your bundle lean:

import { Button } from "@cityofportland/components-react/button";
import "@cityofportland/components-react/button.css";

export function Example() {
  return <Button>Continue</Button>;
}

Developing

turbo build --filter=@cityofportland/components-react
turbo dev --filter=@cityofportland/components-react
turbo storybook --filter=@cityofportland/components-react
turbo test --filter=@cityofportland/components-react

Storybook runs on port 6006, and stories live right alongside the components they document. Tests run through Vitest with Playwright for browser-based checks.

When you add or change a component, keep its behavior, accessibility, styles, story, and tests moving together as one unit, and reach for the shared types and CSS packages instead of duplicating values locally.

License

MIT