Always build both Tailwind CSS bundles
What does this MR do and why?
Always build both Tailwind CSS bundles
This ensures that both tailwind.css and tailwind_cqs.css are built
when running the GDK. This meands that the
USE_TAILWIND_CONTAINER_QUERIES doesn't need to be set manually anymore
as both bundles are guaranteed to be available.
This makes it easier to toggle between both states of the
tailwind_container_queries feature flag.
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
rm app/assets/builds/tailwind*.cssgdk start- Both bundles should get created in
app/assets/builds/. - As you change utils within the app, both bundles should update.
Faster validation
gdk stop vite && rm app/assets/builds/tailwind*.cssgdk start vite- Wait for
app/assets/builds/tailwind*.cssfiles to be built -
diff -u --color app/assets/builds/tailwind*.cssshould show MQs and CQs in diff.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.