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

saficss

v0.2.0

Published

Tiny runtime CSS-in-JS for plain HTML. Write a style object, get a class name. No build step.

Readme

SafiCSS

Tiny runtime CSS-in-JS for plain HTML. You write your styles as a JavaScript object, call one function, and it styles the element. No build step, no framework. Drop it in any HTML file over a CDN, or install it from npm. It reaches all of CSS: hover, media queries, and keyframes, not only inline styles.

css(object) turns the object into real CSS, generates a class name, injects the rules into one <style> tag, and hands back the class. The same object always gets the same class, so nothing is duplicated. Because it injects a class instead of an inline style string, pseudo-classes, media queries, and animations all work.

  • Zero runtime dependencies
  • Ships TypeScript types, so your editor autocompletes property names and flags bad values
  • About 1.3 KB gzipped
  • Works from npm and from a CDN, as an ES module or a plain <script> global

Install

npm i saficss
import { css } from "saficss";

document.getElementById("box").className = css({
  background: "#444",
  color: "#fff",
  padding: 16,
});

Use from a CDN

ES module

<div id="box"></div>
<script type="module">
  import { css } from "https://esm.sh/saficss";

  const accent = "#22d3ee"; // a normal JS variable

  document.getElementById("box").className = css({
    background: "#444",
    color: accent,
    padding: 16,
    borderRadius: 8,
    "&:hover": { background: "#666" },
    "@media (max-width: 600px)": { padding: 8 },
  });
</script>

Plain script tag (global)

Load the IIFE build and use window.SafiCSS:

<div id="box"></div>
<script src="https://cdn.jsdelivr.net/npm/saficss/dist/saficss.global.js"></script>
<script>
  document.getElementById("box").className = SafiCSS.css({
    background: "#444",
    color: "#fff",
    padding: 16,
  });
</script>

Serve it straight from GitHub

jsDelivr serves any file in the repo without an npm publish. Point at a tag or commit for a stable URL:

<!-- ES module -->
<script type="module">
  import { css } from "https://cdn.jsdelivr.net/gh/Abdulkader-Safi/[email protected]/dist/saficss.mjs";
</script>

<!-- Global script -->
<script src="https://cdn.jsdelivr.net/gh/Abdulkader-Safi/[email protected]/dist/saficss.global.js"></script>

Change @v0.1.0 to whatever tag you want. The built files live in dist/ and are committed to the repo, so these URLs work as soon as the tag is pushed. Forking this? Swap Abdulkader-Safi/SafiCSS for your own owner/repo.

For production, pin a version (never @latest) and add Subresource Integrity to the <script> tag: integrity="sha384-..." crossorigin="anonymous". jsDelivr shows the hash for any file on its page.

API

css(styleObject) => string

Returns a class name. Injects the rules once, keyed by a hash of the object.

const cls = css({
  color: "white",
  padding: 16,
  "&:hover": { color: "cyan" },
  "& span": { fontWeight: 700 },
  "@media (max-width: 600px)": { padding: 8 },
});
el.className = cls;

Key rules:

  • Property keys are CSS properties in camelCase (backgroundColor) or kebab strings ("background-color"). Both work, and camelCase is what gives you autocomplete and typo-catching.
  • String and number values become declarations. A number gets px, except for the unitless properties React treats specially (opacity, zIndex, fontWeight, lineHeight, flex, order, gridColumn, and the rest). Custom properties (--foo) never get a unit.
  • An object value is a nested block. A key starting with & is replaced by the generated class: "&:hover", "& > a", "& span", "&.active". A key starting with @ is an at-rule (@media, @supports). Nest descendant selectors with &, so "& span", not a bare "span". That prefix is what lets TypeScript tell a real selector from a misspelled property.
  • An array value sets fallbacks for one property (display: ["grid", "flex"]).

keyframes(framesObject) => string

Injects an @keyframes block and returns the animation name. Use it in an animation value.

const spin = keyframes({
  from: { transform: "rotate(0deg)" },
  to: { transform: "rotate(360deg)" },
});

el.className = css({ animation: `${spin} 1s linear infinite` });

injectGlobal(styleObject) => void

Writes unscoped global rules: resets, :root custom properties, body styles. Top-level keys are selectors.

injectGlobal({
  ":root": { "--accent": "#22d3ee" },
  body: { margin: 0, fontFamily: "system-ui" },
  "*": { boxSizing: "border-box" },
});

setVars(vars, target?) => void

Sets CSS custom properties at runtime. Defaults to :root; pass an element to scope them. Define var(--accent) in your styles, then call setVars to change it live. Everything using the variable updates with no re-injection.

setVars({ "--accent": "#f00" }); // on :root
setVars({ accent: "blue" }, myEl); // scoped, "--" added for you

Default export

The default export bundles all four functions, which is what the global build exposes as window.SafiCSS.

import SafiCSS from "saficss";
SafiCSS.css({ color: "red" });

TypeScript

The style object is typed the way React.CSSProperties is, on top of csstype. Property names autocomplete, and a typo or a bad value is a type error:

css({ backgroundColor: "#444" }); // fine, autocompletes
css({ borderColor: 42 }); // Error: number is not assignable to a color
css({ bacgroundColor: "#444" }); // Error: unknown property, the typo is caught
css({ "&:hover": { colr: "red" } }); // Error: typo caught inside nested blocks too

Nested selectors start with & ("&:hover", "& span") and at-rules start with @. That is what lets the compiler separate a real selector from a misspelled property, so typos in property names surface as errors instead of silently producing dead CSS.

That is the linting for anyone using SafiCSS. No stylelint needed for the object API. TypeScript is the linter here. To get it, your editor needs TypeScript running (VS Code does this for .ts and .tsx files out of the box), and you import from the package so the bundled saficss.d.ts types apply.

Development

npm run typecheck   # tsc --noEmit
npm run lint        # eslint
npm run test        # vitest
npm run build       # tsup, writes dist/
npm run format      # prettier --write

License

MIT, Abdulkader Safi.