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 🙏

© 2024 – Pkg Stats / Ryan Hefner

postcss-custom-properties-fallback

v1.0.2

Published

Adds fallbacks to your CSS var() functions

Downloads

18,439

Readme

PostCSS Custom Properties Fallback

This plugins adds fallbacks to your CSS Custom Properties and works well as a compantion to PostCSS Custom Properties.

Pop Quiz!

If we remove --color from :root, what color will h1 have in modern browsers?

:root {
-  --color: red;
}

body {
  color: green;
}

h1 {
  color: red;
  color: var(--color);
}

Red or green, expand the right answer (no cheating/googling!):

The text "Wrong answer!" over a cat screaming while firing an automatic rifle

Nope, it's green!

Intuitively it's easy to think that if --color isn't defined, then the browser should skip the color: var(--color) and use the valid color: red above it. Especially since this is what happens in older browsers that don't support CSS Custom Properties.

The right answer is to use the second argument in var() (see Example 10 in the spec), also known as the fallback argument:

color: var(--color, red);

Now it works like expected. See the spec for more information on how invalid/missing values are treated.

The text "Yes!" over a smiling and nodding Jack Nicholson

Right answer! Check the wrong answer to learn why that is.

Usage

Add PostCSS Custom Properties Fallback to your project:

npm install postcss-custom-properties-fallback --save-dev

Use it as a PostCSS plugin:

const postcss = require('postcss');
const postcssCustomPropertiesFallback = require('postcss-custom-properties-fallback');

postcss([postcssCustomPropertiesFallback(/* pluginOptions */)]).process(
  YOUR_CSS /*, processOptions */
);

Options

importFrom

The importFrom option is required. It works like from CSS Custom Properties, except it doesn't support importing from CSS yet.

postcssCustomPropertiesFallback({
  importFrom: { customProperties: { '--color': 'red' } },
});
h1 {
  color: var(--color);
}

/* becomes */

h1 {
  color: var(--color, red);
}