Tailwind just released their new JIT compiler which looks super useful for creating small stylesheets during development. [image] GitHub - tailwindlabs/tailwindcss-jit Contribute to tailwindlabs/tailwindcss-jit development by creating an account on GitHub. I…

So the new JIT Tailwind compiler replaces the need for purging, so that’s one issue. The Hugo stats file is not created until build time, so that will not update realtime. I’d imagine that you would need two terminals running at the same time, one for hugo and one for the JIT compiler.

Right that makes sense. Even still I had issues with running Hugo when trying to do the purge without the hugo stats file and instead using the purge settings from tailwind.config.js It’s possible this could be a Tailwind issue and not necessarily a Hugo issue but wanted to post here in case anyone…

Yeah, so I specify purge settings inside postcss.config.js instead of inside the tailwind.config.js file. I have the post css config point to the hugo stats file. The idea is that Hugo runs the post css process instead of relying on the tailwind plugin to do it. Here is my postcss.config.js which I…

I will find some time to test this, but as I understand it: The JIT compiler is a development thing, so you would somehow have different setups for dev and production There is another thread that mentions this currently failing with Hugo

One of the pros of tailwind jit is that it unifies development and production build processes. It’s still beta, so some people might not be comfortable with using it in production, but its readme explicitly mentions that its designed to be used for both environments. An option to enable writeStats …

[image] raffomania: An option to enable writeStats in server mode would be nice to have to enable this. I have a plan to make TailwindJIT work great with Hugo. I tested it last night (I have a ongoing branch on GitHub), and the current main missing piece is a way to use JIT’s incremental buil…

@bep were you able to make any progress on this?

okay, thank you. seems there is no perfect solution for this yet.

My 3.0 test repo works fine and so far I did not came across any issue. I ported one existing site (that had Tailwind 2.2.* before), no problems found. Purged and minified fingerprinted CSS get’s generated just fine.

Tailwind JIT and Hugo Purge issues

support

angel December 20, 2021, 8:32pm 9

@mhal see Tailwind v3.0 and Hugo

Topic		Replies	Views
Hugo + TailwindCSS purging too aggressively support tailwind	4	1461	November 20, 2021
Tailwind v3.0 and Hugo support	30	13376	August 28, 2023
How to purge TailwindCSS support	4	1069	November 1, 2021
Tailwind CSS JIT support	6	3193	January 18, 2022
Tailwind Starter Announcements tailwind	35	3746	October 6, 2020

Tailwind JIT and Hugo Purge issues

Related topics