Minor Changes
-
192d82a: Add
themeandutilityprops to<Tailwind>for Tailwind v4 CSS-first configuration. Both accept a CSS string and can be combined with the existingconfigprop.import themeCss from "./theme.css?inline"; <Tailwind theme={themeCss}> <div className="bg-brand font-display">Custom themed content</div> </Tailwind>;
Empty strings are no-ops. The base Tailwind theme and utilities are still loaded —
themeandutilitylayer on top.The preview server,
email export, and the caniemail compatibility check all understand the Vite-style?inlineand?rawsuffixes on CSS imports, so the pattern above works the same in your project and inside the preview UI. The compatibility check also extracts thethemeandutilityprops (in addition toconfig) when analyzing your template, so any caniemail incompatibilities in CSS produced by those props will surface as warnings.Internal note: the exported
setupTailwindhelper now takes{ config, cssConfigs }instead of a positionalTailwindConfig. Calling it with the old shape throws with a migration hint.
Patch Changes
- 06f1d05: Watch directories targeted by dynamic
import()template literals so changes to runtime-resolved files trigger preview reloads.