Github url

postcss

by postcss

postcss /postcss

Transforming styles with JS plugins

22.9K Stars 1.2K Forks Last release: 14 days ago (7.0.32) MIT License 2.9K Commits 152 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

PostCSS Gitter

Philosopher’s stone, logo of PostCSS

PostCSS is a tool for transforming styles with JS plugins. These plugins can lint your CSS, support variables and mixins, transpile future CSS syntax, inline images, and more.

PostCSS is used by industry leaders including Wikipedia, Twitter, Alibaba, and JetBrains. The Autoprefixer PostCSS plugin is one of the most popular CSS processors.

PostCSS takes a CSS file and provides an API to analyze and modify its rules (by transforming them into an Abstract Syntax Tree). This API can then be used by plugins to do a lot of useful things, e.g. to find errors automatically insert vendor prefixes.

Support / Discussion: Gitter
Twitter account:@postcss
VK.com page:postcss
中文翻译: [

README-cn.md

](https://github.com/postcss/postcss/blob/master/./README-cn.md)

For PostCSS commercial support (consulting, improving the front-end culture of your company, PostCSS plugins), contact Evil Martiansat [email protected].

Sponsored by Evil Martians

Sponsorship

PostCSS needs your support. We are accepting donationsat Open Collective.

Sponsored by Tailwind CSS

Plugins

Currently, PostCSS has more than 200 plugins. You can find all of the plugins in the plugins list or in the searchable catalog. Below is a list of our favorite plugins — the best demonstrations of what can be built on top of PostCSS.

If you have any new ideas, PostCSS plugin development is really easy.

Solve Global CSS Problem

Use Future CSS, Today

Better CSS Readability

Images and Fonts

Linters

Other

Syntaxes

PostCSS can transform styles in any syntax, not just CSS. If there is not yet support for your favorite syntax, you can write a parser and/or stringifier to extend PostCSS.

Articles

More articles and videos you can find on awesome-postcss list.

Books

Usage

You can start using PostCSS in just two steps:

  1. Find and add PostCSS extensions for your build tool.
  2. Select plugins and add them to your PostCSS process.

CSS-in-JS

The best way to use PostCSS with CSS-in-JS is [

astroturf

](https://github.com/4Catalyzer/astroturf). Add its loader to your

webpack.config.js

:

module.exports = { module: { rules: [{ test: /\.css$/, use: ['style-loader', 'postcss-loader'], }, { test: /\.jsx?$/, use: ['babel-loader', 'astroturf/loader'], } ] } }

Then create

postcss.config.js

:

module.exports = { plugins: [require('autoprefixer'), require('postcss-nested')] }

Parcel

Parcel has built-in PostCSS support. It already uses Autoprefixer and cssnano. If you want to change plugins, create

postcss.config.js

in project’s root:

module.exports = { plugins: [require('autoprefixer'), require('postcss-nested')] }

Parcel will even automatically install these plugins for you.

Please, be aware of the several issues in Version 1. Notice, Version 2 may resolve the issues via issue #2157.

Webpack

Use [

postcss-loader

](https://github.com/postcss/postcss-loader) in

webpack.config.js

:

module.exports = { module: { rules: [{ test: /\.css$/, exclude: /node\_modules/, use: [ { loader: 'style-loader', }, { loader: 'css-loader', options: { importLoaders: 1, } }, { loader: 'postcss-loader' }] } ] } }

Then create

postcss.config.js

:

module.exports = { plugins: [require('precss'), require('autoprefixer')] }

Gulp

Use [

gulp-postcss

](https://github.com/postcss/gulp-postcss) and [

gulp-sourcemaps

](https://github.com/floridoo/gulp-sourcemaps).

gulp.task('css', () =\> { const postcss = require('gulp-postcss') const sourcemaps = require('gulp-sourcemaps') return gulp.src('src/\*\*/\*.css') .pipe( sourcemaps.init() ) .pipe( postcss([require('precss'), require('autoprefixer')]) ) .pipe( sourcemaps.write('.') ) .pipe( gulp.dest('build/') ) })

npm run / CLI

To use PostCSS from your command-line interface or with npm scripts there is [

postcss-cli

](https://github.com/postcss/postcss-cli).

postcss --use autoprefixer -c options.json -o main.css css/\*.css

Browser

If you want to compile CSS string in browser (for instance, in live edit tools like CodePen), just use Browserify or webpack. They will pack PostCSS and plugins files into a single file.

To apply PostCSS plugins to React Inline Styles, JSS, Radium and other CSS-in-JS, you can use [

postcss-js

](https://github.com/postcss/postcss-js) and transforms style objects.

var postcss = require('postcss-js') var prefixer = postcss.sync([require('autoprefixer')]) prefixer({ display: 'flex' }) //=\> { display: ['-webkit-box', '-webkit-flex', '-ms-flexbox', 'flex'] }

Runners

JS API

For other environments, you can use the JS API:

const autoprefixer = require('autoprefixer') const postcss = require('postcss') const precss = require('precss') const fs = require('fs') fs.readFile('src/app.css', (err, css) =\> { postcss([precss, autoprefixer]) .process(css, { from: 'src/app.css', to: 'dest/app.css' }) .then(result =\> { fs.writeFile('dest/app.css', result.css, () =\> true) if ( result.map ) { fs.writeFile('dest/app.css.map', result.map, () =\> true) } }) })

Read the PostCSS API documentation for more details about the JS API.

All PostCSS runners should pass PostCSS Runner Guidelines.

Options

Most PostCSS runners accept two parameters:

  • An array of plugins.
  • An object of options.

Common options:

  • syntax
    : an object providing a syntax parser and a stringifier.
  • parser
    : a special syntax parser (for example, SCSS).
  • stringifier
    : a special syntax output generator (for example, Midas).
  • map
    : source map options.
  • from
    : the input file name (most runners set it automatically).
  • to
    : the output file name (most runners set it automatically).

Treat Warnings as Errors

In some situations it might be helpful to fail the build on any warning from PostCSS or one of its plugins. This guarantees that no warnings go unnoticed, and helps to avoid bugs. While there is no option to enable treating warnings as errors, it can easily be done by adding

postcss-fail-on-warn

plugin in the end of PostCSS plugins:

module.exports = { plugins: [require('autoprefixer'), require('postcss-fail-on-warn')] }

Contributing

Our contributing guidelines will help you with making pull request to this project.

Editors & IDE Integration

VS Code

Atom

Sublime Text

Vim

WebStorm

WebStorm 2016.3 has built-in PostCSS support.

Security Contact

To report a security vulnerability, please use the Tidelift security contact. Tidelift will coordinate the fix and disclosure.

For Enterprise

Available as part of the Tidelift Subscription.

The maintainers of

postcss

and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. Learn more.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.