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

postcss-static-properties

v0.2.2

Published

PostCSS plugin to bake the values of enumerated custom properties

Readme

postcss-static-properties

A very small PostCSS plugin to enable using CSS Custom Properties for static values, which get "baked" down to their simple values in the built CSS.

Rationale

CSS Custom Properties are great, powerful, and really useful for a lot of things. They're also an unnecessary addition when their value will never change:

  • Custom Properties take up a minimum of 8 characters every time they're referenced, so for example using var(--colorWhite) for #fff[^1] increases the size of the (non-gzipped) CSS every time it's used.
  • Every variable used like this pollutes the scope, and risks conflicting with something else on the page accidentally
  • Frankly, not every const needs a publicly-readable name. Sometimes you've got a $blueDarkDarker2 and you just can't get it a better name right now.

For my own use cases, I've ended up using postcss-simple-vars for those types of variables; a holdover from the SASS days. But the CSS ecosystem is increasingly moving toward writing spec-compliant and spec-adjacent CSS, and leaving behind the entirely-distinct syntaxes of things like SASS and LESS. One example is that Stylelint is built to accept a lot of the things PostCSS brings to the table—but, notably, not $dollarVariables. This plugin aims to bridge that gap, allowing reusable consts that are resolved at build time, without breaking the spec.

Options

  • variables (Required): a key-value mapping of names to replacement values. If -- is not prefixed, it will be added.

[^1]: This is an example for brevity; please do not read into the use of a variable for #fff