Skip to content

docs: Remove deprecated nodeAutoUpdate configuration option #5130

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Artur- wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −8
Open

docs: Remove deprecated nodeAutoUpdate configuration option #5130

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions articles/flow/configuration/gradle.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -302,9 +302,6 @@ The Node.js version to be used when Node.js is installed automatically by Vaadin
`nodeDownloadRoot: String = "https://nodejs.org/dist/"`::
URL to download Node.js from. This can be needed in corporate environments where the Node.js download is provided from an intranet mirror. Defaults to `[NodeInstaller.DEFAULT_NODEJS_DOWNLOAD_ROOT]`.

`nodeAutoUpdate: Boolean = false`::
Flag to enable automatic update of the Node.js version installed in `~/.vaadin`, if it's older than the default or defined `nodeVersion`.

`resourceOutputDirectory: File = File(project.buildDir, "vaadin-generated")`::
The output directory for generated non-served resources, such as the token file. Defaults to `build/vaadin-generated`.

Expand Down
7 changes: 2 additions & 5 deletions articles/flow/configuration/maven.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ The Vaadin Maven plugin contains configuration for most configurable properties.

The best way to set persistent configuration properties for a Maven project is to set them in the plugin.

.Enabling Node.js auto-update
.Configuring frontend directory
[source,xml]
----
<plugin>
Expand All @@ -31,7 +31,7 @@ The best way to set persistent configuration properties for a Maven project is t
</execution>
</executions>
<configuration>
<nodeAutoUpdate>true</nodeAutoUpdate>
<frontendDirectory>${project.basedir}/src/main/frontend</frontendDirectory>
Copy link
Contributor

@mcollovati mcollovati Feb 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest using a property with less impact in the application.
For main branch, for example, it could be <frontendExtraFileExtensions>svg,ico</frontendExtraFileExtensions>.

</configuration>
</plugin>
----
Expand Down Expand Up @@ -68,9 +68,6 @@ URL to use for downloading Node.js. In environments behind a firewall, the Node.
`nodeVersion`::
The Node.js version to be used when Node.js is installed automatically. Should be in the format `"v16.0.0"`. Defaults to `FrontendTools.DEFAULT_NODE_VERSION`.

`nodeAutoUpdate`::
Flag to enable automatic update of the Node.js version installed in `~/.vaadin` if it's older than the default or defined `nodeVersion`. Note: any installed version below `should work` is automatically updated regardless of this flag. Defaults to `false`.

`npmExcludeWebComponents`::
Excludes all Vaadin professional and core components from the `package.json`. Lumo theme is not excluded. Excluded packages aren't installed by npm, which makes development bundles smaller. This property alone doesn't remove any Maven dependencies. See <<development-mode/index.adoc#exclude-vaadin-components, Optimize Bundle>> for more information. Defaults to `false`.

Expand Down
Loading