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

bear.css

v0.1.0

Published

Zero-dependency, zero-build atomic CSS utility framework built on a five-level token hierarchy. Native cascade layers, logical properties, fluid type/space scales, container queries.

Readme

bear.css

Bear (or Bare) CSS framework. Same philosophy as b0nes: simple and easy to understand in a day.

The Atomic Stack

  • Level 0 — RAW VALUES (pure numbers, unitless, meaningless alone)
  • Level 1 — PRIMITIVES (raw values given units and meaning)
  • Level 2 — TOKENS (primitives given semantic names)
  • Level 3 — PROPERTIES (tokens applied to CSS properties)
  • Level 4 — COMPOSITIONS (properties that combine intentionally)

Each level only ever references the level below it. Properties never hardcode a primitive directly, compositions never hardcode a property value directly. Change a token, everything built on it updates — that's the whole point.

Structure

├── bear.config.js               ← global framework configuration
├── src/
│   ├── bear.css                 ← entry point, just @imports
│   ├── reset.css
│   ├── primitives/
│   │   ├── index.css            ← entry, just @imports
│   │   ├── scale.css            ← auto-generated
│   │   ├── type.css             ← auto-generated
│   │   └── colors.css
│   ├── tokens/
│   │   └── tokens.css
│   ├── composition/
│   │   └── composition.css
│   └── properties/
│       ├── index.css            ← entry, just @imports
│       ├── space.css
│       ├── layout.css
│       └── responsive.css       ← auto-generated (@media and @container)
├── dist/
│   └── bear.css                 ← the one <link> file, generated
└── package.json

Configuration

The framework is driven by a single JavaScript configuration file: bear.config.js.

module.exports = {
  "scale": [0, 1, 2, 3, 4, 6, 8, 12, 16, 24, 32],
  "base-unit": 4,
  "type-scale-ratio": 1.25,
  "type-base": 16,
  "breakpoints": { "s": 480, "m": 768, "l": 1024, "xl": 1280 }
};

Build

npm run build

The zero-dependency compiler (src/build.js) will:

  1. Dynamically generate the primitive scales (scale.css, type.css) from your config.
  2. Dynamically generate BOTH @media (\@s) and @container (\@c-s) responsive query variants for your defined breakpoints.
  3. Bundle and minify everything into dist/bear.css.

Link that one file in your HTML — src/ is never shipped to a browser.