PostCSS is a tool to transform styles with JS plugins. By @sitnikcode and @evilmartians.

PostCSS 8.4.19 was released. @romainmenke fixed 8.4.17 regression on whitespace preserving after transformations. github.com/postcss/postcss/p… Release’s alchemist by John Collier.
5
7
PostCSS retweeted
PostCSS plugin with the new CSS nesting spec npmjs.com/package/@csstools/…
2
4
Avoid mental gymnastics when it comes to sorting CSS properties with `npm i -D prettier-plugin-css-order postcss` and observe the magic. 🔥
4
11
65
PostCSS retweeted
Replying to @bayes @PostCSS @csswg
We only consider something stable once it has shipped in two browser engines. One engine typically takes lead with a prototype. This will lead to a better understanding of the feature and a solid test suite in WPT. The next engine validates the work of the first.
1
4
PostCSS retweeted
We have published an experimental @PostCSS plugin for the new syntax. Please let us know if you spot any issues or differences with Chrome 109. Once the syntax is stable this will be merged into the regular plugin, npmjs.com/package/@csstools/…
1
4
15
PostCSS retweeted
Hi there! Since our last update the @csswg has resolved to move forward with a more relaxed syntax for nesting.
6
43
269
So I discovered oklch. And it's so great I can't wait for it to be supported natively in all browsers. evilmartians.com/chronicles/…
5
4
Autoprefixer 10.4.13 was released. We fixed a tricky case when Autoprefixer ignores declaration with CSS Custom Properties like --o-rest because it thought that declaration has Opera’s prefix. github.com/postcss/autoprefi… Release’s knight by Vittore Carpaccio.
3
6
If you use CSS nesting and your parser is not PostCSS, please ask your parser authors to make the appropriate breaking changes to the updated nesting syntax ASAP and/or make their parser extensible so others can. Interest is hot, so shipping might be soon. Don’t be a smoosh. 😉
2
1
8
New CSS specifications are coming with powerful features for colors. @sitnikcode, in his new article, explains his 2 favorite features of the new specs: — OKLCH for declaring colors — Native color transformations in CSS evilmartians.com/chronicles/…
3
22
56
With postcss-preset-env polyfill, you can use oklch() colors right now
I published an article about the new oklch() color format in CSS and why it’s better than hex, rgb() or hsl(). Upcoming CSS specs will improve colors a lot (finally, native color modifications). OKLCH color space is one new feature from these specs. evilmartians.com/chronicles/…
5
9
PostCSS retweeted
Welcome back to CSS friends. CSS modules and @PostCSS solved all CSS issues years ago!
1
2
7
PostCSS retweeted
eventually.. a site can ship it's own color profile, like HCT, and then access colors using it. but no browser has that on their radar, it's only in spec land w3.org/TR/css-color-5/#at-pr… you could use the postcss plugin tho github.com/rodydavis/postcss…
1
1
PostCSS retweeted
14.14.0 is out! It adds custom message formatting to the `*-pattern` rules, fixes false positives with two rules, and fixes a few minor bugs. stylelint.io/CHANGELOG#14140
1
2
7
Now we have all PostCSS docs on our website. Thanks to @null_preference postcss.org/docs/writing-a-p…
3
9
PostCSS 8.4.18 was released. Rene Haas fixed ERR_INVALID_FILE_URL_PATH bug on sourceContent: [null] and absolute: true option. github.com/postcss/postcss/p… Release’s alchemy by @ilya_stallone
4
I like A because it has been well researched and has been tested through and through thanks to PostCSS plugins, lightningcss,... We can make PostCSS plugins for terser syntax and it is even possible to improve the native syntax later.
Which of the following best expresses how you want to write nested CSS when it's implemented by browsers? A. I want to use & in every selector, as I think it makes code more clear B. I want to be able to omit & whenever possible, as it's noisy to read and a hassle to type
1
2
PostCSS retweeted
With @PostCSS Extract you can select and export any part of your CSS source to JavaScript. npmjs.com/package/@csstools/…
1
3
4