The Tailwind version is outdated when running `htmgo template`

[bdtomlin]

Currently Tailwind is hard-coded to an old version (3.something) when using the cli and executing htmgo template. It would be nice if it defaulted to the latest version and could be configured in htmgo.yml file.

Here is where it's currently set.

htmgo/cli/htmgo/tasks/css/css.go

Line 81 in 5d9c2f8

url := fmt.Sprintf(`https://github.com/tailwindlabs/tailwindcss/releases/download/v3.4.16/%s`, fileName)

I would be glad to create a pull request if you would like.

Basically I would just add TailwindVersion to the ProjectConfig struct and default it to "latest" and do the plumbing for getting the values from the config file, testing, etc.

Then if the config is latest I would set the URL to

fmt.Sprintf(`https://github.com/tailwindlabs/tailwindcss/releases/latest/download/%s`, fileName)

otherwise...

 fmt.Sprintf(`https://github.com/tailwindlabs/tailwindcss/releases/download/%s/%s`, version, fileName)

[franchb]

Hey @maddalax — I've been working on a more comprehensive take on this. Beyond just making the download URL configurable (as @bdtomlin suggested), I implemented full Tailwind v4 support with backward compatibility for v3 projects.

The main additions:

• tailwind_version field in htmgo.yml (optional — everything auto-detects by default)
• Auto-detection: if input.css contains @tailwind base; directives, it pins to v3.4.16; otherwise defaults to latest (v4)
• Version-aware binary download with sidecar cache file so version changes trigger re-download
• v4 CLI invocation (v4 dropped the -c tailwind.config.js flag)
• Updated CopyAssets to skip tailwind.config.js copy for v4 projects
• Templates, examples, and htmgo-site migrated to v4 CSS-first config
• 22 unit tests for the new version resolution and cache logic

Zero breakage for existing v3 projects — the auto-detection ensures they keep working without any config changes.

PR: #103