Security News
The Risks of Misguided Research in Supply Chain Security
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
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.
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;
}
.foo > .bar {
color: blue;
}
@media (prefers-color-scheme: dark) {
.foo {
color: cyan;
}
}
.foo {
color: pink;
}
Add PostCSS Nesting to your project:
npm install postcss postcss-nesting --save-dev
Use 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
@nest
you definitely want to set theedition
to2021
.
If you are unsure than you should try to omit theedition
option 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 is no longer optionaland
keyword@nest
is removed from the specification2021
This 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 {
color: green;
}
.foo > .bar {
color: blue;
}
@media (prefers-color-scheme: dark) {
.foo {
color: cyan;
}
}
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
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;
}
FAQs
Nest rules inside each other in CSS
The npm package postcss-nesting receives a total of 5,135,713 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 3 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
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.