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

omapps-design-system

v0.2.0

Published

HaHo web design system — CSS tokens, component styles, and DM Sans fonts. Brand-aware (coralCamo, seaLime, mistyRose, blueHaze) and style-aware (light/dark, rounded/sharp).

Readme

omapps-design-system

HaHo web design system. Ships CSS tokens (colors, type, spacing, radii), a component stylesheet (buttons, inputs, lists, badges, toggles), and the DM Sans font family. Brand-aware (coralCamo, seaLime, mistyRose, blueHaze) and style-aware (light/dark, rounded/sharp).

npm install omapps-design-system

Install

Option A — local install (no npm registry needed)

From your app's project root:

npm install ./path/to/design-system

This works for monorepos and private projects. The folder is treated as if it were a published package.

Option B — publish to npm

cd design-system
# either set "name" to a scope you own, e.g. "@yourorg/futevolution-design-system"
# and remove "private": true from package.json
npm publish --access public

Then in the consuming app:

npm install @yourorg/futevolution-design-system

Option C — private GitHub package

Push the design-system/ folder to its own repo and install with:

npm install github:yourorg/futevolution-design-system

Usage

Vite / Next.js / Create React App / any modern bundler

// In your app entry (main.jsx, _app.tsx, etc.)
import "omapps-design-system/styles";

Or import the two stylesheets individually:

import "omapps-design-system/tokens.css";
import "omapps-design-system/components.css";

The fonts (DMSans-*.ttf) are referenced from tokens.css with relative paths and will be picked up automatically by the bundler.

Setting the brand + style

The design system is driven by two attributes on the root element:

<body data-brand="coralCamo" data-style="lightRounded">

Or programmatically:

import { applyTheme } from "omapps-design-system";

applyTheme({ brand: "coralCamo", style: "lightRounded" });

Brands: coralCamo · seaLime · mistyRose · blueHaze Styles: lightRounded · lightSharp · darkRounded · darkSharp

Using tokens in your CSS

All design decisions live in CSS custom properties. Just read them:

.my-card {
  background: var(--surface-card);
  color: var(--text-primary);
  border-radius: var(--radius-lg);
  padding: var(--space-lg);
  font: var(--type-h5);
  letter-spacing: var(--ls-h);
}

.my-button {
  background: var(--button-primary-fill);
  color: var(--button-text-on-primary);
}

When the user switches brand or style, every value above re-tints automatically.

Using component classes

components.css ships pre-styled primitives. Apply them as classes:

<button class="btn btn--big btn--filledA">Continue</button>
<button class="btn btn--medium btn--outlined">Cancel</button>
<button class="icon-btn"><svg>…</svg></button>

(See components.css for the full list — buttons, inputs, lists, badges, toggles, etc.)


File map

design-system/
├── package.json
├── index.js          # entry — imports both CSS files, exports applyTheme()
├── index.css         # if you'd rather only use CSS, @imports both stylesheets
├── tokens.css        # CSS variables (colors, type, spacing, radii, shadows)
├── components.css    # button, input, list, badge, toggle, etc.
└── fonts/
    ├── DMSans-Regular.ttf
    ├── DMSans-Medium.ttf
    └── DMSans-SemiBold.ttf

License

Internal — Futevolution.