You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have picked up the ball and tested what's needed to get Tailwind 3 up and running with Hugo Pipes, and I was pleasantly surprised that it was mostly working (if we look pasted the Tailwind JIT compiler).
The main missing issue is that we need to somehow trigger rebuilds of the CSS when the templates changes. This is unfortunate and we should try to find a more effective way to do it, but Tailwind 3 seems to be very fast -- and we can make this behaviour optional.
This proposal should also be generally useful to others, as it will make the current "cache busting" logic on CSS/JSS etc. changes more transparent and configurable.
I will fill in some more details as I test this out in a real project.
The text was updated successfully, but these errors were encountered:
I have picked up the ball and tested what's needed to get Tailwind 3 up and running with Hugo Pipes, and I was pleasantly surprised that it was mostly working (if we look pasted the Tailwind JIT compiler).
The main missing issue is that we need to somehow trigger rebuilds of the CSS when the templates changes. This is unfortunate and we should try to find a more effective way to do it, but Tailwind 3 seems to be very fast -- and we can make this behaviour optional.
This proposal should also be generally useful to others, as it will make the current "cache busting" logic on CSS/JSS etc. changes more transparent and configurable.
I will fill in some more details as I test this out in a real project.
The text was updated successfully, but these errors were encountered: