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

@greese/ui

v1.2.0

Published

greese ui's CSS and design tokens: a framework-free stylesheet, per-component CSS, custom properties, Sass kit and TypeScript constants. Works in plain HTML, or under any framework.

Readme

@greese/ui

greese ui's CSS and design tokens, with no framework attached. Use it from plain HTML, or under any framework: @greese/react renders the same markup, and the Svelte, Vue and Angular packages will too (ADR 0014).

npm install @greese/ui
<link rel="stylesheet" href="node_modules/@greese/ui/dist/greese.css" />
<!-- or, with a bundler: import '@greese/ui/styles.css' -->

<button class="greese-Button greese-Button--solid">Save changes</button>

Each component's classes, parts, modifiers and state attributes are listed in the docs' Styling sections (and in style-manifest.json), and they're a public contract: every framework package renders the same ones. Native elements need nothing else (<dialog>, <details>, form controls); widgets with keyboard behaviour (Tabs, Combobox…) also need JavaScript, which the framework packages provide.

What's in it

| Import | What | | ------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | @greese/ui/styles.css | Tokens and every component's styles | | @greese/ui/base.css | Opt-in reset and page defaults | | @greese/ui/css/<Name>.css | One component's own styles (plus the shared core). A component built on others (a Dialog uses Button) needs theirs too; the framework packages wire that up | | @greese/ui/tokens.css | --greese-* custom properties, in @layer greese.tokens | | @greese/ui/palette.css | Opt-in: the palette as --greese-<hue>-<shade> (--greese-lavender-600), about 1.5 kB compressed | | @greese/ui/scss | The whole stylesheet as Sass, configurable (@use 'pkg:@greese/ui/scss' with ($breakpoints: …)) | | @greese/ui/scss/kit | The theming kit: @use 'pkg:@greese/ui/scss/kit' as greese, build-time themes that reject unknown names | | @greese/ui/scss/tokens | The token CSS, plus $breakpoints and $space-keys Sass maps | | @greese/ui/scss/layers | Only the cascade layer order statement | | @greese/ui/scss/maps | Only the Sass maps ($breakpoints, $space-keys, every token default as $color and $scalars, the palette as $palette, and $layer-order); emits no CSS | | @greese/ui/scss/mixins, tones, floating, controls, slides | The library's own mixins and maps for theme authors (ADR 0021); emit no CSS | | @greese/ui/scss/utilities | The utility classes from Sass, built with the configured breakpoints: @include utilities.classes(…) | | @greese/ui/scss/core, scss/components/<Name> | For a Sass build that picks its components: core (tokens, type system) and one component's own stylesheet | | @greese/ui/css/resets.css | Opt-in: .greese-reset-color, -shape, -motion and .greese-reset, which take a theme's layers back from part of a page | | @greese/ui/theme-files | A theme as data (Theme Studio's JSON) and the SCSS it becomes: specToLayout(), the documented folder of modules, or specToScss(), one file (ADR 0034) | | @greese/ui/style-manifest.json | Every component's styling API, read from the compiled CSS | | @greese/ui | TypeScript constants (color, palette and each hue, space, radius, lineHeight, shadow, breakpoints, …), createTheme() and getSchemeScript() |

It has no dependencies.

Colors follow the OS color scheme. data-greese-scheme="light" or "dark" on any element forces a mode for that subtree, and modes can be nested. createTheme() builds a scoped theme as a static CSS string, which you can serve however you like and apply with data-greese-theme="<name>".

Color roles and the palette

color holds the semantic roles components use. The brand colors, in order, are primary (what components use for interactive emphasis), secondary, tertiary and accent, each with …Strong and a WCAG-safe …Content color that createTheme derives when you set only the main color.

palette is 22 hues × 11 shades (50–999). Use it instead of hex literals: palette.lavender[600] or import { lavender } from '@greese/ui' in TypeScript, lavender-600 in the SCSS kit, var(--greese-lavender-600) with palette.css.