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

@paul-portfolio/css

v0.8.1

Published

Framework-agnostic CSS components for the Paul Design System

Readme

@paul-portfolio/css

The stylesheet layer of the Paul Design System. Plain CSS, driven by the design tokens in @paul-portfolio/tokens. Use it on its own with your own markup, or pair it with @paul-portfolio/react, whose components render the class names this package styles.

Install

npm install @paul-portfolio/css @paul-portfolio/tokens

Entry points

Import the tokens first (they define the CSS custom properties everything else reads), then one of the CSS entry points:

import "@paul-portfolio/tokens/tokens.css";

// Everything: reset + base element styles + components
import "@paul-portfolio/css/index.css";

// Or just the components, when you already have a reset
// (e.g. Tailwind's preflight):
import "@paul-portfolio/css/components.css";

| Entry | Contents | |-------|----------| | index.css | reset + base + components | | components.css | component styles only (no reset/base) | | reset.css | a minimal CSS reset | | base.css | base element and typography styles |

Using the classes

Every component is a base class plus modifiers. A few examples:

<button class="btn btn--primary">Save</button>
<button class="icon-btn" aria-label="Close">✕</button>

<div class="input__wrapper">
  <label class="input__label" for="email">Email</label>
  <input id="email" class="input" />
</div>

<textarea class="textarea"></textarea>

<button class="switch switch--on" role="switch" aria-checked="true">
  <span class="switch__thumb"></span>
</button>

<span class="spinner" role="status" aria-label="Loading"></span>
<hr class="divider" />

Component classes

btn · icon-btn · input · textarea · chip · switch · badge · avatar · card · modal · tooltip · info-tip · skeleton · spinner · divider

Each lives in its own file under src/components/ and is bundled into components.css. Variants follow a block--modifier convention (btn--primary, icon-btn--sm, divider--vertical).

Tokens

Colors, spacing, radii, typography, and motion all come from CSS custom properties like --paul-color-primary-600 and --paul-spacing-2, defined by @paul-portfolio/tokens. Override those variables to theme the whole system.

License

MIT © Paul Sumido