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

sulphuris

v4.0.0

Published

An adaptable CSS utility library

Readme

Sulphuris logo

Sulphuris

npm version build status license

An adaptable CSS utility library

[!NOTE] Sulphuris sits somewhere between the old-school utility libraries Bootstrap and Primer on one side and on the other Tailwind.

Sulphuris is built around a single _config.scss file that defines almost all utility class generation. It is basically design tokens but in scss. By overriding these configuration variables, you can customize breakpoints, colors, spacing, and more — tailoring the framework to each project's specific needs.

📖 Docs

Highlights

  • Design tokens - A single SCSS _config.scss containing the variables that dictate which utilities will be generated. You can wire your Figma design tokens to directly override the config variables (with a bit of work, or simply use poops.
  • Less !important usage - abstaining from !important usage as much as possible.
  • Spacing size classes named in pixels - e.g. .pt-32 results in padding-top: 2rem; (32px at the default root), and .pt--32 in padding-top: -2rem;. The number in the class name is a design token, not the unit. Opt into $size-aliases and steps of the scale also answer to a t-shirt name — .pt-sm is .pt-8. Numeric aliases are deliberately not offered: .pt-2 is 2px here and 8px in Bootstrap and Tailwind.
  • XXL screen breakpoint - from 1680px. Or even larger. You can add any number of breakpoints.
  • Docs that cannot drift - the Class Reference page is generated, not written: script/gen-reference.mjs parses the built dist/sulphuris.css and emits every selector with its declarations, so what is documented is literally what Sass produced.
  • REM units - sizes, font sizes, breakpoint widths and the container/grid metrics all emit rem, so a layout scales with the reader's browser font-size setting instead of ignoring it (px only responds to zoom). All of it is still written in px and converted at emit time, so config overrides stay px. Border widths stay px — 2px at a 20px root is 2.5px, straddling a device pixel. Nothing writes an absolute font-size to the root, so the reader's browser setting is what rem resolves against. $rem-units: false reverts the lot without moving a class name.

🚀 Getting Started

Install

$ npm install sulphuris

Usage

Uses SCSS modules (@use/@forward) for better scoping and tree-shaking. This makes it a bit difficult to override the config variables, but future proofs the usage (meaning dart-sass v3).

To bundle Sulphuris utilities with your project you can use:

@use "sulphuris";

In order to configure Sulphuris you must override the default configuration, before the @use 'sulphuris'; line.

The list of config variables you can override or negate (turn off) can be seen in the default config file: core/_config.scss

@forward "sulphuris/core/config" with (
  $colors: (
    black: #000000,
    white: #ffffff,
    primary: #824f2d,
    brownish: #dcc8ac,
    muted: #6d6d6d,
  ),
  $breakpoints: (
    ...,
  )
);

@use "sulphuris";

Overriding the default configuration with create the style utility classes tailored for your project.

Legacy imports

Previously Sulphuris used the oldschool imports and overrides making it super easy to place your own overrides.

In your main SCSS file, import Sulphuris:

@import "_config.scss"; // Import your own configuration, it overrides the default one src/core/_config.scss so you can change only the variables you need
@import "sulphuris";

Be sure to include the node_modules directory in your sass include paths. This is usually done in your build tool configuration.

💻 Local Development

The build process is powered by Poops, a simple and fast build and bundle tool for modern web development.

Running the local server

This project requires node and npm installed. To setup the project run npm install.

$ script/server

Will start a local development server. It will also watch for the changes and rebuild the project when necessary. script/server only serves the repo root, where /docs/ does not exist yet.

Generating docs

To develop or build the docs use either following:

$ script/docs        # build + serve on :4041 with live reload
$ script/docs -b     # build once, no server

The Class Reference page is generated, not written — script/gen-reference.mjs parses the built dist/sulphuris.css and emits every selector with its declarations, so it cannot drift from what Sass actually produces.

Publishing

$ script/publish

Will run the publish script which will lead you through the npm publishing process. It can increment the version, build the code, tag it and create a new GitHub release (make sure that you have gh GitHub CLI installed and authentified).

Publishing GitHub action is set to publish to NPM when a new release is created.

📝 Contributing

If you have any ideas on how to improve Sulphuris, feel free to open an issue or a pull request. Contributions welcome!

ToDo:

  • [ ] Sort out the resets, they need to be reactive to margin and padding utilities (and other utilities)
  • [x] Aliases — shipped as $size-aliases (t-shirt names, opt-in). Numeric ones were dropped on purpose: pt-2 already means 2px here and 8px in Bootstrap/Primer, so the same class in copied markup would mean two paddings
  • [ ] Inline links
  • [ ] Animations and transitions
  • [ ] Form elements

Why

It's 2021. After years of making websites I realized I'm copy/pasting a set of utilities that were growing as the time progressed. Primer and Bootstrap were a bit too stubborn for my taste just because I wanted something like that but configurable to the extreme. Something that will adapt to every project that I embark on. So I made my own.

P.S. I found out about Tailwind a while later. I'm not a guy who follows the news. And even then I preferred the old school, cause sometimes it gets hard to swim in Tailwind class soup.

Name

Sulphuris is a Latin word for sulfur. Sulfur is a chemical element. Elemental sulfur at room temperature is a bright yellow, crystalline solid.

Sulphur is one of three components of lapis philosophorum, the philosopher's stone. Other two are mercury and salt. Sulphur is the soul of the stone, mercury is the spirit and salt is the body.

I was very interested in alchemy and the philosopher's stone when I was a kid. Fascinated by the idea of achieving immortality. And after I matured a bit I realized that the philosopher's stone is a metaphor for the state of enlightenment and inner balance. And that achieving immortality is not about living forever, but about living a meaningful life. Because infinite time means death of meaning.

I noticed that this aspect of the tria prima (three primes) is ambiguous and can be interpreted in many ways. Like the three primes of front-end development: HTML, CSS and JavaScript. So I decided to name this project Sulphuris. Where JavaScript is the spirit, HTML is the body and CSS is the soul - Front-end philosopher's stone.

But then if we look the tria prima from perspective of the web development front-end would represent the soul, back-end would represent the spirit and the database would represent the body. This means that one philosopher's stone can be made of many other philosopher's stones, and so on. Like a fractal. That's Alchemy.

~Fullstack Alchemist :laughing:

License

MIT 2021 @stamat