refactor!: stop auto-running vaadinPrepareFrontend in development mode#24119
Merged
mcollovati merged 1 commit intomainfrom Apr 15, 2026
Merged
Conversation
IDE-triggered Gradle builds (e.g. IntelliJ compiling on file change) were running `vaadinPrepareFrontend` via `processResources`, which interfered with the running Vite dev server and broke hotdeploy. Since Vaadin 25, the dev server handles frontend preparation at runtime, so the task no longer needs to run automatically. The previous behavior can be restored by setting `alwaysExecutePrepareFrontend = true`. Fixes #24108
|
caalador
approved these changes
Apr 15, 2026
mcollovati
deleted the
issues/24108-prevent_automatic_run_of_prepareFrontendTask
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
IDE-triggered Gradle builds (e.g. IntelliJ compiling on file change) were running
vaadinPrepareFrontendviaprocessResources, which interfered with the running Vite dev server and broke hotdeploy.Since Vaadin 25, the dev server handles frontend preparation at runtime, so the task no longer needs to run automatically. The previous behavior can be restored by setting
alwaysExecutePrepareFrontend = true.Fixes #24108