Sorry for PostCSS 7→8 update nightmare. Major release always was a problem in PostCSS. A good part of PostCSS 8 release. that we fixed a few problems in this update. We hope 8→9 update will be much easier, because of the 8.0 changes. evilmartians.com/chronicles/…

I was actually thinking about postCSS plugin that will replace every border-radius with: ``` --current-border-radius: N; border-radius: var(--current-border-radius); ``` So then you can use this variable your media components

Perhaps this might save my fellow Rails devs some time trying to get Tailwind 2 running: the latest published webpacker version (5.2.1) relies on postcss-loader 3.0.0, which won't load PostCSS 8. So installing rails/webpacker from master it is🤠

For anyone using Tailwind CSS v2.0 with PostCSS 7, we had to change how we publish the compatibility build due to some bone-headed assumptions I made about semver calculations 🙃 Should fix issues you might be having! Updated installation details here: tailwindcss.com/docs/install…

PostCSS 8.1.8 was released. @ludovicofischer fixed LazyResult type compatibility with Promise. github.com/postcss/postcss/p… Task came from our chat. We are always welcome to any questions. gitter.im/postcss/postcss Release’s alchemist by Maxim Kozlov. artstation.com/maximyz

Tailwind v2 uses PostCSS v8 so I updated the package. When I started Next.js dev server, a PostCSS plugin called Autoprefixer stopped working. I updated Next.js to v10 and that fixed it.

⚡️ If you are upgrading @tailwindcss v2 and @PostCSS v8 on #Vite apps. Here is a workaround to get them to work TODAY: github.com/vitejs/vite/pull/…

Everything you need to know about Tailwind CSS v2.0 is in the announcement post here 👉 blog.tailwindcss.com/tailwin… Check it out, play with it, and let us know what you think!

13.8.0 is out! It adds 2 new rules, 1 new option and fixes 2 sets of bugs. Additionally, the `report*` flags and options, e.g. `--reportNeedlessDisables`, now produce standard lint violations. stylelint.io/changelog#1380

Think we’ve got a solution to this for now. We’re going to publish a PostCSS 7 compatible version as well under a “compat” tag: npm install tailwindcss@compat ...if you’re using a framework that hasn’t upgraded yet. Nice thing is we’re able to do it in the same branch.

Sad news from Travis CI: blog.travis-ci.com/2020-11-0… I moved @Logux, @Browserslist, @Autoprefixer, @PostCSS to GitHub Actions. My config with the color fix, Yarn cache in one line, full test just for latest Node.js version and quick tests for other versions: github.com/logux/core/blob/n…