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-cli-recursive

v3.1.3

Published

CLI for PostCSS

Downloads

5

Readme

npm node deps tests cover code style chat

npm i -g|-D postcss-cli
postcss [input.css] [OPTIONS] [-o|--output output.css] [-w|--watch]

⚠️ If there are multiple input files, the --dir or --replace option must be passed.

cat input.css | postcss [OPTIONS] > output.css

⚠️ If no input files are passed, it reads from stdin. If neither -o, --dir, or --replace is passed, it writes to stdout.

|Name|Type|Default|Description| |:---|:--:|:-----:|:----------| |-d, --dir|{String}|undefined|Output Directory| |-b, --base|{String}|undefined|Use together with --dir for keeping directory structure.| |-x, --ext|{String}|extname(output)|Output File Extension| |-o, --output|{String}|undefined|Output File| |-r, --replace|{String}|undefined|Replace Input <=> Output| |-p, --parser|{String}|undefined|Custom PostCSS Parser| |-s, --syntax|{String}|undefined|Custom PostCSS Syntax| |-t, --stringifier|{String}|undefined|Custom PostCSS Stringifier| |-w, --watch|{Boolean}|false|Enable Watch Mode| |--poll|{Boolean}|false|Use polling for file watching| |-u, --use|{Array}|[]|PostCSS Plugins| |-m, --map|{Boolean}|{ inline: true }|External Sourcemaps| |--no-map|{Boolean}|false|Disable Sourcemaps| |-e, --env|{String}|process.env.NODE_ENV|Sets $NODE_ENV| |-c, --config|{String}|dirname(file)|PostCSS Config Path postcss.config.js| |-h, --help|{Boolean}|false|CLI Help| |-v, --version|{Boolean}|false|CLI Version|

ℹ️ More details on custom parsers, stringifiers and syntaxes, can be found here.

Config

If you need to pass options to your plugins, or have a long plugin chain, you'll want to use a configuration file.

postcss.config.js

module.exports = {
  parser: 'sugarss',
  plugins: [
    require('postcss-import')({...options}),
    require('postcss-url')({ url: 'copy', useHash: true })
  ]
}

Note that you can not set the from or to options for postcss in the config file. They are set automatically based on the CLI arguments.

Context

For more advanced usage it's recommend to to use a function in postcss.config.js, this gives you access to the CLI context to dynamically apply options and plugins per file

|Name|Type|Default|Description| |:--:|:--:|:-----:|:----------| |env|{String}|'development'|process.env.NODE_ENV| |file|{Object}|dirname, basename, extname|File| |options|{Object}|map, parser, syntax, stringifier|PostCSS Options|

postcss.config.js

module.exports = (ctx) => ({
  map: ctx.options.map,
  parser: ctx.file.extname === '.sss' ? 'sugarss' : false,
  plugins: {
    'postcss-import': { root: ctx.file.dirname }),
    'cssnano': ctx.env === 'production' ? {} : false
  }
})

⚠️ If you want to set options via CLI, it's mandatory to reference ctx.options in postcss.config.js

postcss input.sss -p sugarss -o output.css -m

postcss.config.js

module.exports = (ctx) => ({
  map: ctx.options.map,
  parser: ctx.options.parser,
  plugins: {
    'postcss-import': { root: ctx.file.dirname },
    'cssnano': ctx.env === 'production' ? {} : false
  }
})