Skip to content

Commit 6222254

Browse files
authored
Update README.md to add context around Tailwind 4 and PostCSS
Tailwind 4's CLI tool no longer supports the `--postcss` flag. This updates the documentation to add a note about the change, and hopefully points folks in the right direction.
1 parent 7fb4975 commit 6222254

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

README.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -353,6 +353,9 @@ Than use `@plugin` annotation in `app/assets/tailwind/application.css`:
353353
```
354354
355355
### Using with PostCSS
356+
> [!NOTE]
357+
> Starting with Tailwind 4, the TailwindCSS CLI tool no longer supports PostCSS out of the box, as the `--postcss` command has been removed. The below information only partains to Tailwind 3.
358+
> If you're wanting to leverage PostCSS with Tailwind 4, you'll likely want to reference [The official Tailwind 4 PostCSS docs](https://tailwindcss.com/docs/installation/using-postcss), and leverage [cssbundling-rails](https://github.com/rails/cssbundling-rails).
356359
357360
If you want to use PostCSS as a preprocessor, create a custom `postcss.config.js` in your project root directory, and that file will be loaded by Tailwind automatically.
358361

0 commit comments

Comments
 (0)