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

@orangecheck/design

v0.18.0

Published

OrangeCheck design system — multi-theme tokens, primitives, and family composites for the .ochk.io sub-sites. Tailwind 4 + Next.js Pages Router. Not for third-party integration.

Readme

@orangecheck/design

The OrangeCheck design system — multi-theme tokens, primitives, and family composites for the .ochk.io sub-sites. Tailwind 4 + Next.js Pages Router. Family-internal (for embeddable OrangeCheck components see @orangecheck/react).

Living showcase: design.ochk.io (Storybook). Canonical design + rollout plan: ~/Projects/ochk/DESIGN-SYSTEM-PLAN.md.

What's in the box

| Subpath | Contents | |---------|----------| | @orangecheck/design | everything below, re-exported | | @orangecheck/design/tokens | OcThemeProvider, useOcSkin, OcThemePicker, getOcThemeInitScript, OC_THEMES, DEFAULT_OC_THEME, cn | | @orangecheck/design/primitives | Button Badge Input Label Alert Textarea ThemeToggle Working ErrorBoundary (cva + Radix) | | @orangecheck/design/components | family composites, re-exported from @orangecheck/ui | | @orangecheck/design/styles.css | token bridge + base layer + utility system + all skin token values |

Two theme axes

  • Modelight | dark, owned by next-themes via the .dark class. Toggle with <ThemeToggle />. Unchanged from today.
  • Skin — a named theme (orangecheck default, midnight, …), owned by <OcThemeProvider> via the data-oc-theme attribute, persisted in the oc_skin cookie at Domain=.ochk.io so a choice carries across every family site. Pick with <OcThemePicker />.

The two compose: any skin renders in both modes.

Adoption (consumer site)

src/styles/globals.css:

@import 'tailwindcss';
@source '../../node_modules/@orangecheck/ui';
@source '../../node_modules/@orangecheck/design';
@import 'tw-animate-css';
@custom-variant dark (&:is(.dark *));
@import '@orangecheck/design/styles.css';

_app.tsx:

<ThemeProvider attribute="class" defaultTheme="system" enableSystem>
    <OcThemeProvider>
        {/* …app… */}
    </OcThemeProvider>
</ThemeProvider>

_document.tsx <Head> (avoids a skin flash before hydration):

<script dangerouslySetInnerHTML={{ __html: getOcThemeInitScript() }} />

Header (gate the picker behind a flag during staged rollout):

<ThemeToggle />
{process.env.NEXT_PUBLIC_OC_THEME_PICKER === '1' && <OcThemePicker />}

Fonts are still loaded by the app via next/font into --font-sans-display and --font-mono-display, exactly as before.

Adding a skin

  1. Add src/styles/themes/<id>.css declaring the full token set for both modes (under [data-oc-theme='<id>'] and [data-oc-theme='<id>'].dark).
  2. @import it from src/styles/themes.css.
  3. Add a row to OC_THEMES in src/tokens/themes.ts.
  4. Publish. Every site picks it up on the next Renovate bump — no per-site edits.

Build

yarn build          # tsup (cjs+esm+dts) + copy CSS to dist/styles
yarn type-check
yarn storybook      # local showcase
yarn build-storybook

Published via tag design-v<x.y.z> from oc-packages (see release.yml). MIT.