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

@openish/theme

v0.0.1

Published

The --openish-* style-hook layer: a self-contained default palette, plus a Jack Henry Design System binding.

Readme

@openish/theme

Every colour, font and spacing value openish resolves, as --openish-* custom properties.

One stylesheet is the whole styling requirement:

<link rel="stylesheet" href="@openish/theme/index.css" />

Nothing is fetched. Fonts are the platform's own stacks, so there is no font host to allow and nothing to self-host.

Why a package rather than component CSS

A shadow root inherits a page's custom properties but not its class rules. That split is the whole design: tokens travel into every shadow root openish renders, selectors do not. It is also a trap paid for once already — the syntax-highlight colours lived here for three milestones and coloured nothing, because .hljs-keyword in a host stylesheet never matches inside a shadow root. The rules are component CSS now and the --openish-hl-* hooks stayed here.

For the same reason index.css includes the highlight hooks rather than leaving them to a second import: a host that followed the README got body-coloured code blocks and nothing to suggest why.

Choosing a scheme

Dark follows the reader's system preference by default. To decide it yourself, put a class on <html> — either beats the media query, so either one is final:

document.documentElement.classList.toggle('openish-dark', scheme === 'dark')
document.documentElement.classList.add('openish-light')  // never dark, whatever the OS says

Jack Henry

For a page that already has the Jack Henry Design System on it, import @openish/theme/jh.css instead — the same hooks, bound to JH alias tokens, so openish inherits that page's palette rather than sitting next to it in its own. @jack-henry/jh-core is a peer dependency of that entry only; the default entry has no dependencies at all.

Entries

| Import | What it is | |---|---| | @openish/theme / /index.css | The default: layout, tokens and highlight hooks, self-contained | | /jh.css | The same hooks bound to Jack Henry alias tokens | | /tokens.css, /layout.css, /highlight.css | The three halves of the default entry, separately | | /light.css, /dark.css | One scheme only, for a page that has already decided | | /fonts.css | Opt-in font declarations |

Licence

MIT.