Great article, thanks. You can also use the selector-max-* rules, e.g. selector-max-id, to indirectly limit nesting as these rules resolve the nesting selector. They also disallow writing out overly complex selectors in longhand:
stylelint.io/user-guide/rule…stylelint.io/user-guide/rule…
Great article looking at how native CSS nesting works, some differences between it and preprocessor nesting, some of the pitfalls you can run into with it, and how you can start using it today with PostCSS
CSS nesting is (finger crossed) coming to browsers!
I wrote an article that's part introduction, part explainer on how to use it today with @PostCSS and part tips on preventing coding yourself into a corner due to specificity.
Check it out here: kilianvalkhof.com/2021/css-h…
CSS nesting is (finger crossed) coming to browsers!
I wrote an article that's part introduction, part explainer on how to use it today with @PostCSS and part tips on preventing coding yourself into a corner due to specificity.
Check it out here: kilianvalkhof.com/2021/css-h…
I've been using postcss-preset-env with spec-compatible nesting (for the most part) for years now and I'm very happy with it.
The dangerous things is people nesting 10 or so levels deep, making very long, overly specific selectors.
CSSTree validator plugin for VS Code gives more precision about a place of a problem in CSS property value and can be used in conjunction with stylelint
marketplace.visualstudio.com…
This issue popped up after my tweet. I’d love it if there were something I could attach to my licenses that assured folks there are no barriers or hindrances.
I want to encourage & help these folks; not put them at odds with their legal team.
github.com/postcss/postcss/i…
A few times a year, I’ll receive a message from an enthusiastic team whose legal folks flag one of my OSS libraries for CC0-1.0. Is there some attachment I can add to ensure they are good?
I don’t want to go MIT & force people to credit me or contribute back.
Very convenient rules for automatically sorting and grouping properties in your CSS code by @theKashey.
Your eyes will get used to the order and read the source code faster.
github.com/theKashey/styleli…
Autoprefixer 10.3.1 was released.
@luke_warlow disabled prefixes for `content` property because it could contain any text inside.
github.com/postcss/autoprefi…
Release’s knight by Lucas Cranach.
Autoprefixer 10.3 was released. @luke_warlow added ::file-selector-button support.
github.com/postcss/autoprefi…
Release name is “Чести своей не отдам никому” (I will give my honor to no one), the motto of Pskov city of Russia.
Autoprefixer 10.3 was released. @luke_warlow added ::file-selector-button support.
github.com/postcss/autoprefi…
Release name is “Чести своей не отдам никому” (I will give my honor to no one), the motto of Pskov city of Russia.