Package Exports

postcss-normalize

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (postcss-normalize) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

PostCSS Normalize

PostCSS Normalize lets you automatically include the parts of normalize.css you need, based upon your project’s browserlist.

Usage

Add PostCSS Normalize to your build tool:

npm install postcss-normalize --save-dev

Add a browserlist entry in your package.json:

{
  "browserslist": "last 2 versions"
}

Node

Use PostCSS Normalize to process your CSS:

require('postcss-normalize').process(YOUR_CSS, { /* options */ });

PostCSS

Add PostCSS to your build tool:

npm install postcss --save-dev

Use PostCSS Normalize as a plugin:

postcss([
    require('postcss-normalize')({ /* options */ })
]).process(YOUR_CSS, /* options */);

Gulp

Add Gulp PostCSS to your build tool:

npm install gulp-postcss --save-dev

Use PostCSS Normalize in your Gulpfile:

var postcss = require('gulp-postcss');

gulp.task('css', function () {
    return gulp.src('./src/*.css').pipe(
        postcss([
            require('postcss-normalize')({ /* options */ })
        ])
    ).pipe(
        gulp.dest('.')
    );
});

Grunt

Add Grunt PostCSS to your build tool:

npm install grunt-postcss --save-dev

Use PostCSS Normalize in your Gruntfile:

grunt.loadNpmTasks('grunt-postcss');

grunt.initConfig({
    postcss: {
        options: {
            use: [
                require('postcss-normalize')({ /* options */ })
            ]
        },
        dist: {
            src: '*.css'
        }
    }
});