tree 9568daa2fefa7cdef0ec5416fc734b640822ecc3
parent 0635c776054d5ced92328a2c8cd4014ef5f4a86f
author Sean McCullough <banksean@gmail.com> 1750879928 +0000
committer Autoformatter <bot@sketch.dev> 1750880552 +0000

webui: generate tailwind.css in esbuild.go, output to dist/

Move Tailwind CSS generation from npm script to esbuild.go build process
and output generated file to dist/tailwind.css instead of src/tailwind.css
to prevent tracking generated files in git.

Problems Solved:
- Generated CSS file was tracked in git causing unnecessary diffs
- Build process relied on manual npm script execution
- Generated CSS mixed with source files

Solution Architecture:
- Integrated Tailwind CSS generation into Go build process
- Moved output location to dist/ directory (already gitignored)
- Added automatic CSS generation during webui.Build()
- Moved @tailwindcss/cli from devDependencies to regular dependencies

Implementation Details:
- Added generateTailwindCSS() function to run tailwindcss CLI during build
- Modified Build() to call generateTailwindCSS() after npm ci
- Updated file copying logic to skip src/tailwind.css (no longer needed)
- Moved @tailwindcss/cli to regular dependencies to work with --omit dev
- Updated npm tailwind script to output to dist/tailwind.css
- Added src/tailwind.css to .gitignore to prevent accidental tracking

Files Modified:
- sketch/webui/esbuild.go: Added CSS generation and updated build process
- sketch/webui/.gitignore: Added src/tailwind.css exclusion
- sketch/webui/package.json: Moved @tailwindcss/cli to dependencies, updated script
- sketch/webui/src/tailwind.css: Removed from git tracking

The generated CSS is now properly separated from source files and
automatically created during the build process.

Co-Authored-By: sketch <hello@sketch.dev>
Change-ID: s3464450fc2c7851fk