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

PostCSS retweeted
📊 How do you compile your CSS in your Tailwind projects? A. PostCSS integrated into my framework/build tool (Next.js, webpack, Vite, Parcel, etc.) B. Separately with postcss-cli C. Separately with the Tailwind CLI D. I use the CDN, bandwidth is free isn't it?
79% Integrated PostCSS
6% postcss-cli
7% Tailwind CLI
7% I just use the CDN 🤠
4,078 votes • Final results
21
8
68
documented how to upgrade to the last webpacker (so I can move from postcss 7 to postcss 8 with the vulnerability fixed)
1
3
4
PostCSS 7 plugins works. The only problem is that PostCSS 8 plugins will work always after PostCSS 7, which affects on some plugins interactions, when one plugin was ported to PostCSS 8 before another
1
PostCSS retweeted
For example, currently you could get a warning about outdated vulnerable postcss, but you can do nothing about this, because of create-react-app: github.com/facebook/create-r… They already have a fix, but have not released it for 2 months already
1
1
1
Adding dependencies to Result#messages (to PostCSS runner watch for file changes) is now part of plugins guidelines. We also standardize message for folder dependency. Thanks to @bradlc for the guideline changes. github.com/postcss/postcss/p…
1
I've just contributed to stylelint. Consider supporting them too — every little helps! opencollective.com/stylelint via @opencollect
2
1
Even the last browsers has at least 35 features in CSS with vendor prefixes. List of all actual prefixes or why @Autoprefixer is needed in 2021: css-tricks.com/is-vendor-pre…
5
7
If you have “TypeError: Cannot read property 'prefix_exceptions' of undefined” try to update caniuse-lite by: npx browserslist@latest --update-db This bug was fixed in the latest release.
3
3
PostCSS Theme UI looks neat. Define design tokens → use them in your CSS as values github.com/nelonoel/postcss-…
1
5
22
We started caniuse-lite refactoring to solve a few security issues. github.com/browserslist/cani… For a while there will be no Can I Use database updates for Browserslist and @Autoprefixer. You can support this refactoring on: opencollective.com/browsersl…
3
3
What a ride! The bit about color & unit length types is gold — so true, so important — it made me wanna spin up a new window & start writing types for PostCSS. Then they talked @ container queries & even my polyfill — accurate of issues + kind in tone. ❤️ f-word.dev/episodes/11/
5
10
I’m unbiased. The obvious answer is postcss-bob-ross-palette. npmjs.com/package/postcss-bo…
What are MUST have PostCSS plugins? We're currently just using postcss-nesting
1
1
5
Replying to @stolinski
We still need Auoprefixer css-tricks.com/is-vendor-pre… I also always add postcss-momentum-scrolling github.com/solversgroup/post…
4
8
What are MUST have PostCSS plugins? We're currently just using postcss-nesting
13
2
39
The new postcss-icon-blender plugin by @SomeSchmidt suggests an interesting mix of developer experience of Font Awesome and new best practices of SVG. github.com/icon-blender/post…
5
7
We're a lot closer to not having to bother with vendor prefixes, but there are still 35 things left that still need it. 28 if you drop IE 11.
6
43
264
We are using Size Limit to prevent client-side build of PostCSS from bloating of unnecessary dependencies. github.com/ai/size-limit/
PostCSS 8.2.14 was released. Barak Igal reduced client-side PostCSS (30 KB → 23 KB) by removing source-map which we do not use anyway in this mode. github.com/postcss/postcss/p… Engraving with release’s alchemist by Pieter Bruegel the Elder. metmuseum.org/art/collection…
1
4
2