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

boss-css

v0.0.26

Published

Polymorphic, usage-driven CSS-in-JS.

Readme

Table of Contents

Key Features

  • Polymorphic $$ authoring with framework-aware runtime adapters.
  • Style props and className parsing in one unified API.
  • Strong generated TypeScript types for style props and prepared components.
  • Plugin-driven parser and prop pipeline (parser, prop, strategy, use).
  • Server output and browser runtime support with configurable strategy behavior.
  • Zero-runtime compilation
  • Runtime-only mode for client CSS injection when needed.
  • Token support, pseudo selectors, media/breakpoint props, and nested child selectors.
  • CLI tooling for init/compile/dev workflows.

Quick Start

Install and scaffold:

npx boss-css init

Import the generated runtime once near your app root:

import './.bo$$'

Examples

Write styles directly with $$:

export default function Demo() {
    return (
        <$$
            display="flex"
            gap={12}
            padding={16}
            borderRadius={12}
            backgroundColor="#111"
            color="#fff"
            hover={{ backgroundColor: '#222' }}
        >
            Hello Boss CSS
        </$$>
    )
}

ClassName syntax (prop:value tokens):

export function Badge() {
    return (
        <span className="display:inline-block padding:6_10 border-radius:999 color:white background-color:#ed4b9b">
            New
        </span>
    )
}

Grouped pseudo and responsive className:

export function Button() {
    return (
        <button className="mobile:hover:{color:white;background-color:black} hover:{text-decoration:underline;color:red}">
            Hover me
        </button>
    )
}

Mix static className and dynamic props:

export function Mixed({ bgColor }: { bgColor: string }) {
    return <div className="display:flex gap:12 border-radius:12" backgroundColor={bgColor} />
}

Compose className conditionals with cx:

import { cx } from 'boss-css/variants'

const className = cx('display:flex gap:8', { 'hover:color:purple': true })

Bosswind plugin for Tailwind-like utilities:

const Box = () => <div className="flex w:100 bg:blue-500 p:4 hover:bg:blue-700">Tailwind-like Box using classNames</div>

const BoxProps = () => (
    <$$ flex width="100" bg="blue-500" p="4" hover={{ bg: 'blue-700' }}>
        Tailwind-like Box using props
    </$$>
)

Strategy Modes

Boss CSS supports multiple output strategies:

  • inline-first (default): Inline everything that's possible => smallest CSS output, lowest possible unused styles, instant critical CSS.
  • classname-first: Use class names everywhere possible, variables for dynamic cases.
  • classname-only: Static class parsing with zero runtime output. (aka TailwindCSS).
  • runtime: Runtime-only or hybrid behavior, for cases where styles need to be generated at runtime.

Read more: https://bosscss.com/docs/concepts/runtime-strategy

License

MIT