Since Tailwind v3.0.11+, Hugo Pipes work perfectly to build CSS and no longer error out because of JIT mode. This was mentioned here by @praveenjuge as well as me. So, that solves the issue for production builds.
However, Hugo doesn’t trigger a CSS rebuild on a template change and simply rebuilds only the changed template/file (which is the desired behaviour with most tools). But since Tailwind v3+ pretty much requires a rebuild on every template change, this becomes a problem in development.
I tried disabling file caches, and the
--disableFastRender flag, but that doesn’t do the trick.
Is there any way to trigger a (specific) resource re-build with every single file change/server reload instead of using a cached copy?
This would make the workflow much cleaner by reducing the need for npm scripts and/or other tools/steps to build the CSS in development. It would reduce the toolchain’s update latency as well.