package
Nest rules inside each other in CSS
npm install postcss-nestingGitHub-flavored package documentation.
Across all versions.
Download trend unavailable.
Runtime metadata.
Tagged topics.
npm install postcss-nesting --save-dev
PostCSS Nesting lets you nest style rules inside each other, following the CSS Nesting specification.
If you want nested rules the same way Sass works you might want to use PostCSS Nested instead.
.foo {
color: red;
&:hover {
color: green;
}
> .bar {
color: blue;
}
@media (prefers-color-scheme: dark) {
color: cyan;
}
color: pink;
}
/* becomes */
.foo {
color: red;
}
.foo:hover {
color: green;
Add PostCSS Nesting to your project:
npm install postcss postcss-nesting --save-devUse it as a PostCSS plugin:
const postcss = require('postcss');
const postcssNesting = require('postcss-nesting');
postcss([
postcssNesting(/* pluginOptions */)
]).process(YOUR_CSS /*, processOptions */);The CSS nesting feature has gone through several iterations and what is currently implemented in browsers is not the same as what was originally proposed. This plugin dates back to the original proposal and you might have written your CSS expecting this older behavior.
You can pick the older behavior by setting the edition option.
The edition values correspond with rough dates when of a particular version of the specification:
2024-02 (default)2021[!TIP] If you wrote nested rules with
@nestyou definitely want to set theeditionto2021.
If you are unsure than you should try to omit theeditionoption and use the default.
Eventually we will remove support for the older edition, and this plugin option, so it is strongly advised to update your CSS to the latest edition.
postcssNesting({
edition: '2024-02'
})2024-02 (default):is() pseudo-class in the generated CSS is no longer optional. However you can add postcss-is-pseudo-class to transpile furtherand keyword@nest is removed from the specification2021This version is a continuation of what existed before CSS nesting was implemented in browsers.
It made a few non-invasive changes to keep up with implementations but it is falling behind.
.foo {
color: red;
&:hover {
color: green;
}
> .bar {
color: blue;
}
@media (prefers-color-scheme: dark) {
color: cyan;
}
color: pink;
}
/* becomes */
.foo {
color: red;
color: pink;
}
.foo:hover
2021)Before :
#alpha,
.beta {
&:hover {
order: 1;
}
}After without the option :
postcssNesting():is(#alpha,.beta):hover {
order: 1;
}.beta:hover has specificity as if .beta were an id selector, matching the specification.
After with the option :
postcssNesting({
noIsPseudoSelector: true
})#alpha:hover, .beta:hover {
order: 1;
}.beta:hover has specificity as if .beta were a class selector, conflicting with the specification.
Before :
.alpha > .beta {
& + & {
order: 2;
}
}After without the option :
postcssNesting():is(.alpha > .beta) + :is(.alpha > .beta) {
order: 2;
}After with the option :
postcssNesting({
noIsPseudoSelector: true
}).alpha > .beta + .alpha > .beta {
order: 2;
}this is a different selector than expected as .beta + .alpha matches .beta followed by .alpha.
avoid these cases when you disable :is().
writing the selector without nesting is advised here.
/* without nesting */
.alpha > .beta + .beta {
order: 2;
}alaguna
sombragriselros@gmail.com
Estimated unpacked size across 5 packages.
285.5 kB
Includes dependencies.