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

node-css-by-js

v0.0.1

Published

Turn your CSS into JS that turns it into CSS.

Readme

CSS by JS

The next iteration of CSS-in-JS. Turn your CSS into JS that turns it into CSS.

Description

This a CLI tool that will turn a CSS file into JS, which will then apply the styles to the DOM when loaded in the browser. So, you write CSS, but you never load a single *.css file onto your page. It's left to JS, which is doing eveything else these days anyway.

For example, this CSS:

:root {
  --my-color: #1a1a1a;
}

body,
html {
  font-family: "Source Sans Pro", sans-serif;
  background: linear-gradient(45deg, #f5d9ff, #fefdff);
  color: var(--my-color);
}

main {
  text-align: center;
  max-width: 700px;
  margin: 0 auto;
}

h1,
h3 {
  margin: 0;
}

Turns into this, which is then passed to a applyCSS function:

[
  { name: ":root", properties: [{ name: "--my-color", value: "#1a1a1a" }] },
  {
    name: "body, html",
    properties: [
      { name: "font-family", value: "'Source Sans Pro', sans-serif" },
      { name: "background", value: "linear-gradient(45deg, #f5d9ff, #fefdff)" },
      { name: "color", value: "var(--my-color)" }
    ]
  },
  {
    name: "main",
    properties: [
      { name: "text-align", value: "center" },
      { name: "max-width", value: "700px" },
      { name: "margin", value: "0 auto" }
    ]
  },
  { name: "h1, h3", properties: [{ name: "margin", value: "0" }] }
];

And when the output is loaded on your page, you get styles:

<script src=".output/css-by-js.js"></script>

alt text

Installation

npm install css-by-js

Usage

You just need to pass in a reference to a CSS file, as well as location where the file will be outputted.

css-by-js --file=./assets/sample.css --output=./assets/output.js

A --file is required. If no --output is specified, a css-by-js.js file will be created in the current directory.

Support

I can't imagine it works perfectly in every scenario, but I've designed the tool to handle simple element CSS rules (div{}), pseudo-elements, and even CSS custom properties. If you find an oddball out there, make file an issue or make a contribution.

Why would I use this?

I'll leave that up to you.

License

MIT © Alex MacArthur