From a4073274ee14cb6f5a9ce9367e35642a1169265b Mon Sep 17 00:00:00 2001 From: Marco Collovati Date: Fri, 24 Jul 2026 10:42:31 +0200 Subject: [PATCH] docs: Update Gradle frontendOutputDirectory details (#5827) Clarify the requirements for frontendOutputDirectory in the Gradle configuration. --- articles/flow/configuration/gradle.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/flow/configuration/gradle.adoc b/articles/flow/configuration/gradle.adoc index bb37946170..7b43cbc840 100644 --- a/articles/flow/configuration/gradle.adoc +++ b/articles/flow/configuration/gradle.adoc @@ -274,7 +274,7 @@ Whether to generate a production bundle even if an existing pre-compiled bundle Enables development using the frontend development server instead of an application bundle. This applies only to development mode. This must be set in the `vaadin {}` block; the Gradle plugin does not read the corresponding `vaadin.frontend.hotdeploy` property from `application.properties`. `frontendOutputDirectory: File = null`:: -The folder where Vite should output [filename]`index.js` and other generated files. Defaults to `null`, which uses the automatically detected value of the main SourceSet, usually `build/resources/main/META-INF/VAADIN/webapp/`. +The folder where Vite should output [filename]`index.js` and other generated files. Defaults to `null`, which uses the automatically detected value of the main SourceSet, usually `build/resources/main/META-INF/VAADIN/webapp/`. A custom value must end in `META-INF/VAADIN/webapp` (e.g. `build/my-frontend/META-INF/VAADIN/webapp/`); otherwise the production build fails with an error. `npmFolder: File = project.projectDir`:: The folder where the [filename]`package.json` file is located. Defaults to the project root directory.