PostCSS & Tailwind
The postcss key runs a PostCSS pipeline. It is separate from the
Sass styles pipeline โ use it for Tailwind CSS,
Autoprefixer, or any other PostCSS plugin.
Warning
PostCSS and its plugins are not bundled with Poops. Install what you use in your own project:
npm i -D postcss @tailwindcss/postcss tailwindcss.
Shape
{
"postcss": {
"in": "src/css/main.css",
"out": "dist/css/main.css",
"options": {
"plugins": ["@tailwindcss/postcss"],
"minify": true
}
}
}
in/outโ input and output CSS files.options.pluginsโ array of plugin names. Each is a string, or a tuple["name", { opts }].options.minify/options.justMinifiedโ same behaviour as the other pipelines.
Pass options to a plugin with the tuple form:
{
"postcss": {
"in": "src/css/main.css",
"out": "dist/css/main.css",
"options": { "plugins": [["autoprefixer", { "grid": true }]] }
}
}
Tailwind CSS v4
Install the deps, then your entry CSS just imports Tailwind:
@import "tailwindcss";
Config:
{
"postcss": {
"in": "src/css/main.css",
"out": "dist/css/main.css",
"options": { "plugins": ["@tailwindcss/postcss"], "minify": true }
},
"markup": {
"in": "src/markup",
"out": "dist",
"options": { "includePaths": ["_layouts", "_partials"] }
},
"watch": ["src"]
}
Then use Tailwind utility classes in your markup. Tailwind v4 auto-detects content sources, so no
tailwind.config.js is required.
Info
Build order matters. PostCSS runs after Styles and Markups. That is deliberate โ Tailwind scans the compiled HTML for utility classes, so the markup must exist first. In watch mode, editing a template re-triggers the PostCSS pass.
Sass and Tailwind together
Keep them as two pipelines writing to two files: Sass compiles your .scss, PostCSS handles
Tailwind independently. They don't need to chain.
If you do want PostCSS to post-process the Sass output (say, Autoprefixer over compiled Sass),
point postcss.in at the Sass output file and postcss.out at a different file so the
original isn't overwritten mid-build.
Tip
Most projects want either Sass or Tailwind, not both. Reach for the styles pipeline for
authored SCSS, and the postcss pipeline for utility-first Tailwind.
Next: React.