Adding or removing Tailwind classes in Java code does not result in new production bundle

[sissbruecker]

Description of the bug

Flow does not infer that adding or removing Tailwind classes in Java code requires recompiling the Tailwind CSS and thus building a new production bundle. As such, after the first prod bundle is built any change to class names in Java code results in broken styling as the respective CSS for those classes is missing.

Expected behavior

Flow should probably always build a new prod bundle when Tailwind is enabled.

Minimal reproducible example

• Download a starter with v25
• Add the CSS class bg-lime-100 to an element
• Run mvn install
• Change the CSS class to bg-lime-200
• Run mvn install
• Start the app from the built JAR file
• Observe that the element does not have a background color

Versions

• Vaadin / Flow version: 25