PostCSS Preset Env lets you convert modern CSS into something most browsers can understand, determining the polyfills you need based on your targeted browsers or runtime environments.
npm install postcss-preset-env
@custom-media --viewport-medium (width <= 50rem);
@custom-selector :--heading h1, h2, h3, h4, h5, h6;
:root {
--mainColor: #12345678;
}
@media (--viewport-medium) {
body {
color: var(--mainColor);
font-family: system-ui;
overflow-wrap: break-word;
}
:--heading {
background-image: image-set(url(img/heading.png) 1x, url(img/[email protected]) 2x);
margin-block: 0;
}
}
a {
color: rebeccapurple;
&:hover {
color: color-mod(var(--mainColor) alpha(80%));
}
}
/* becomes */
@media (max-width: 50rem) {
body {
color: rgba(18, 52, 86, 0.47059);
font-family: system-ui, -apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Oxygen, Ubuntu, Cantarell, Fira Sans, Droid Sans, Helvetica Neue;
word-wrap: break-word;
}
h1, h2, h3, h4, h5, h6 {
background-image: url(img/heading.png);
margin-top: 0;
margin-bottom: 0;
}
}
@media (max-width: 50rem) and (-webkit-min-device-pixel-ratio: 2), (max-width: 50rem) and (min-resolution: 192dpi) {
h1, h2, h3, h4, h5, h6 {
background-image: url(img/[email protected]);
}
}
a {
color: #639
}
a:hover {
color: rgba(18, 52, 86, 0.8);
}
Without any configuration options, [postcss-preset-env] enables stage 3 features and supports all browsers.
Add PostCSS Preset Env to your build tool:
npm install postcss-preset-env --save-dev
Use PostCSS Preset Env to process your CSS:
require('postcss-preset-env').process(YOUR_CSS);
Add PostCSS to your build tool:
npm install postcss --save-dev
Use PostCSS Preset Env as a plugin:
postcss([
require('postcss-preset-env')()
]).process(YOUR_CSS);
Add Gulp PostCSS to your build tool:
npm install gulp-postcss --save-dev
Use PostCSS Preset Env in your Gulpfile:
var postcss = require('gulp-postcss');
gulp.task('css', function () {
return gulp.src('./src/*.css').pipe(
postcss([
require('postcss-preset-env')()
])
).pipe(
gulp.dest('.')
);
});
Add Grunt PostCSS to your build tool:
npm install grunt-postcss --save-dev
Use PostCSS Preset Env in your Gruntfile:
grunt.loadNpmTasks('grunt-postcss');
grunt.initConfig({
postcss: {
options: {
use: [
require('postcss-preset-env')()
]
},
dist: {
src: '*.css'
}
}
});
The stage
key determines which CSS features to polyfill, based upon their
position in the process of becoming implemented web standards found at [cssdb].
The stages are 0 through 5. You can specify false
to ignore all stages and
rely on [features][#features] exclusively.
require('postcss-preset-env')({
stage: 0
})
The features
key determines which CSS features to polyfill based upon their
unique specification id found at [cssdb]. Pass true
to enable a feature, and
pass false
to disable a feature. Pass an object {}
to configure options of
an individual polyfill. Any features not explicitly toggled here will be
determined by [stage][#stage].
require('postcss-preset-env')({
stage: false,
features: [ 'css-nesting' ]
})
The browsers
key determines the browsers to support, which will enable or
disable polyfills based upon their support matrix found at [caniuse].
By default, [postcss-preset-env] will inherit any existing browserslist config,
.browserslistrc config, browserslist section in package.json, or browserslist
environment variables.
require('postcss-preset-env')({
browsers: 'last two versions'
})
The insertBefore
and insertAfter
keys allow you to insert other PostCSS
plugins along the chain. This is highly valuable if you are also using sugary
PostCSS plugins that must execute between plugins within postcss-preset-env.
Both insertBefore
and insertAfter
support chaining one or multiple plugins.
require('postcss-preset-env')({
insertBefore: {
'css-color-modifying-colors': require('postcss-simple-vars')
}
})