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 🙏

© 2025 – Pkg Stats / Ryan Hefner

postcss-variables-rewrite

v0.0.2

Published

PostCSS plugin for rewriting the variables path in @import

Downloads

7

Readme

PostCSS Variables Rewrite Build Status

PostCSS plugin for rewriting the variables path in @import. Its main purpose is to provide theme support in the webpack build process.

Why to use it

Imagine that you develop UI reusable component pattern library. You have centralized handling of the color palette but you need to have local mapping of that palette to the component styles. So that you have the possibility to do the following:

Button/css/Button.scss

@import './variables';

.button--color-primary {
  background-color: $primary;
}

Button/css/variables.scss

@import '~styles/colors/colors';

$primary: $green;

Button/css/variables.blue.scss

@import '~styles/colors/colors';

$primary: $blue;

This plugin will provide an easy way to rewrite the @import statement so that during the build process we can build separate bundles for each theme. Scoping styles to component level is very important and handling theme in not direct way is even more important.

Usage

postcss([ require('postcss-variables-rewrite')({
  originalValue: './variables',
  targetValue: './variables.blue'
})])

webpack

{
  loader: 'postcss-loader',
  options: {
    ident: 'postcss',
    plugins () {
      return [
        require('postcss-variables-rewrite')({
          originalValue: './variables',
          targetValue: './variables.blue'
        })
      ]
    }
  }
}

Where targetValue can be defined based on the env variable in our case: yarn build --env.theme=blue

See PostCSS docs for examples for your environment.