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

@box-kite/core

v2.1.0

Published

The Box Kite styling engine, with no framework at all — runtime atomic CSS for a plain-DOM app, a Web Component or another framework.

Downloads

605

Readme

@box-kite/core

The Box Kite styling engine, with no framework at all. It generates atomic CSS at runtime and caches every rule by its content, so the same value anywhere in a page reuses one class.

This is the package a plain-DOM app, a Web Component or another framework's adapter installs. Using React? Install @box-kite/react instead — it depends on this and re-exports it, so you get one copy of the engine and the Box component with it.

npm install @box-kite/core
import { createStyleEngine } from '@box-kite/core';

const engine = createStyleEngine();

document.querySelector('#card').className = engine.classNames({
  p: 4,
  bgColor: 'blue-500',
  borderRadius: 2,
  hover: { bgColor: 'blue-600' },
});

That is the whole runtime: no build step, no provider, no effects. Rules reach the document on their own microtask — flushSync() is for reading computed styles in the same tick, and getStyles() for static output with no DOM in the process at all.

Your own props and components

BoxExtends.extend() registers a prop or a value; the types come from the /types entry:

// types.d.ts
import { ExtractBoxStyles } from '@box-kite/core/types';
import { extendedProps } from './myProps';

declare module '@box-kite/core/types' {
  namespace Augmented {
    interface BoxProps extends ExtractBoxStyles<typeof extendedProps> {}
  }
}

@box-kite/core/types is the augmentation target for React projects too — the registry being extended lives here, not in the binding.

Links

MIT