Security News
ESLint is Now Language-Agnostic: Linting JSON, Markdown, and Beyond
ESLint has added JSON and Markdown linting support with new officially-supported plugins, expanding its versatility beyond JavaScript.
postcss-nesting
Advanced tools
The postcss-nesting package is a PostCSS plugin that allows you to use nesting syntax in CSS, similar to what is offered by preprocessors like Sass and Less. It helps to write more readable and maintainable CSS by allowing styles to be nested within one another.
Nesting Rules
Allows nesting of selectors within a parent selector, which will be expanded to the equivalent of 'a b { color: black; }'.
a {
& b { color: black; }
}
Nesting Properties
Enables nesting of properties, which is useful for grouping font properties or other related properties together.
a {
font: {
weight: bold;
size: 1em;
family: serif;
}
}
Nesting At-Rules
Supports nesting of at-rules like @media within a selector, which will be processed into the correct CSS syntax.
a {
@media (min-width: 500px) {
color: black;
}
}
Similar to postcss-nesting, postcss-nested allows for nesting of selectors within CSS. It follows the nesting rules of preprocessors like Sass rather than the CSS Nesting Module.
This package includes postcss-nesting as one of its features, among other future CSS features, and allows you to use them in current browsers.
This is a syntax plugin for PostCSS that allows you to work with SCSS syntax, including nesting, but it does not compile SCSS. It's useful for linting SCSS with stylelint and PostCSS.
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.
a, b {
color: red;
& c, & d {
color: white;
}
}
/* becomes */
a, b {
color: red;
}
a c, a d, b c, b d {
color: white;
}
Add PostCSS Nesting to your project:
npm install postcss-nesting --save-dev
Use PostCSS Nesting to process your CSS:
import postcssNesting from 'postcss-nesting';
postcssNesting.process(YOUR_CSS /*, processOptions, pluginOptions */);
Or use it as a PostCSS plugin:
import postcss from 'postcss';
import postcssNesting from 'postcss-nesting';
postcss([
postcssNesting(/* pluginOptions */)
]).process(YOUR_CSS /*, processOptions */);
PostCSS Nesting runs in all Node environments, with special instructions for:
Node | Webpack | Create React App | Gulp | Grunt |
---|
You can also use PostCSS Nesting on Deno:
import postcss from "https://deno.land/x/postcss/mod.js";
import postcssNesting from "https://cdn.jsdelivr.net/npm/postcss-nesting@10/mod.js";
await postcss([postcssNesting]).process(YOUR_CSS /*, processOptions */);
Before :
#alpha,
.beta {
&:hover {
order: 1;
}
}
After without the option :
postcssNesting()
:is(#alpha,.beta):hover {
order: 1;
}
.beta:hover
has specificity as if .beta
where 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
where 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;
}
The CSS Nesting Module spec states on nesting that "Declarations occuring after a nested rule are invalid and ignored.".
While we think it makes sense on browsers, enforcing this at the plugin level introduces several constrains that would
interfere with PostCSS' plugin nature such as with @mixin
FAQs
Nest rules inside each other in CSS
The npm package postcss-nesting receives a total of 5,169,121 weekly downloads. As such, postcss-nesting popularity was classified as popular.
We found that postcss-nesting demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
ESLint has added JSON and Markdown linting support with new officially-supported plugins, expanding its versatility beyond JavaScript.
Security News
Members Hub is conducting large-scale campaigns to artificially boost Discord server metrics, undermining community trust and platform integrity.
Security News
NIST has failed to meet its self-imposed deadline of clearing the NVD's backlog by the end of the fiscal year. Meanwhile, CVE's awaiting analysis have increased by 33% since June.