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

@exodra/style

v0.1.0

Published

Build CSS style strings from objects for Exodra's `style` prop — camelCase, auto-px, custom properties, conditionals. Zero dependencies.

Readme

@exodra/style

Build CSS style strings from objects, so you don't hand-write the style prop. Pure and zero-dependency — the output is a plain string that drops straight into Exodra's static.style / bindable.style (works in the DOM and in SSR).

npm install @exodra/style

Usage

import { style } from '@exodra/style';

h('div', { static: { style: style({ color: 'red', fontSize: 12, '--gap': 8 }) } });
// style="color:red;font-size:12px;--gap:8"

Rules

  • camelCase → kebab-case: backgroundColorbackground-color.
  • numbers get px — except 0 and unitless properties (opacity, zIndex, lineHeight, fontWeight, flex, order, …) and --custom properties.
  • arrays expand: padding: [4, 8]padding:4px 8px.
  • falsy values are skipped: null / undefined / false → dropped (great for conditionals). A falsy argument is skipped too.
  • raw strings are appended verbatim; later arguments win in the browser.
// conditional + merge
style(base, isActive && { color: 'blue' }, { opacity: hidden ? 0 : 1 });

// reactive styles — just call it inside a derive
bindable({ style: derive(theme, (t) => style({ color: t.fg, padding: [4, 8] })) });

Why a string?

Exodra's style prop is a plain string in the schema — the same value works whether the tree is rendered to the DOM or to HTML on the server. style() is just the ergonomic front-end; there's no runtime coupling to a renderer.


📖 Full documentation: exodra.org