How to configure tailwind v4 in Go project, as standalone build step.

[theKlisha]

Hi! I'm maintaining golang project and I use tailwind in html templates. With version v3.4.17 I could run tailwindcss -o $(STYLESHEET_MIN) --minify in my Makefile, provided I had tailwind.config.js file with the following content:

/** @type {import('tailwindcss').Config} */
module.exports = {
  content: ["./**/*.templ", "./**/*.html"],
  includeLanguages: { templ: "html" },
};

But this approach does not seem to work in version 4. I'm forced to provide input file with -i flag. I could live with it but only one file at the time can be provided this way, forcing me to use some other CSS preprocessing tool together with tailwind. Is there a way for me to upgrade without complicating build process by including additional tooling/dependencies?

[wongjn]

Indeed, an input CSS file is required by the CLI.

[theKlisha]

Ok, so as I understand it right now, since v4 there is no way for tailwind to aggregate input files, to produce one single css output file, without additional tools, external to tailwind itself. Do I understand it correctly?

[wongjn]

You can @import all CSS files from one main CSS file, and use that main CSS file as the input file in the tailwindcss command.