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-rewrite-composes

v1.0.0

Published

Rewrites aliased paths used in your CSS Modules composes rules to the correct path

Downloads

15

Readme

PostCSS Rewrite Composes

The problem

When using your own internal component library or libraries like Tachyons & Basscss, with PostCSS + CSSModules you often want to compose the utility classes from these libraries to build more complex components in your app.

However what you don't want to do is have to write paths like the following:

  .Tachyons {
    composes: aspect-ration from 'tachyons/src/_aspect-ratios.css';
    composes : bg-right from 'tachyons/css/tachyons.css';
  }
  .Basscss {
    composes: mr2 from 'basscss/css/basscss.css';  
  }
  .MyFramework {
    composes: Input from 'MyFramework/build/es6/Input/Input.css';
  }

Instead we would like to write them like to write them like this

  .Tachyons {
    composes: aspect-ration from 'tachyons/_aspect-ratios.css';
    composes : bg-right from 'tachyons/tachyons.css';
  }
  .Basscss {
    composes: mr2 from 'basscss/basscss.css';  
  }
  .MyFramework {
    composes: Input from 'MyFramework/Input/Input.css';
  }

So that they match our JS imports

  import Input from 'MyFramework/Input/Input.js'

While it's true you could use an alias in webpack for building your bundle and even use it for running test. I prefer to run test separate of webpack when developing and use a similar plugin for babel that also rewrites my imports based on wether I'm running the code in webpack or running it in my test suit. By this I mean my component library has both an es6 build and commonjs build. Webpack uses the former and mocha the later.

Example Usage

  import rewireComposes from 'postcss-rewrite-composes'
  postcss([rewireComposes({
    prefix: 'mercury-storybook',
    subPath: 'build/es6'
  })])

Run npm run example to see example output.

Options

prefix

  • Type: string
  • Alias path prefix Note no slashes at the end of the prefix.

subPath

  • Type: string
  • Subpath removed when you wrote your aliased composes rules. Note no slashes at the beginning or end of the subpath.