fix: Update parameters

Update missing parameters and
add to the table mode the
parameter targets and
system property written out
for clarity

Closes #4041

Author: caalador

articles/flow/configuration/properties.adoc

@@ -95,156 +95,360 @@ When a system property and a servlet parameter have the same name, the system pr
 [[properties]]
 == Properties Defined
 
-The following table contains the properties that are defined in the [classname]`com.vaadin.server.DeploymentConfiguration` and [classname]`com.vaadin.flow.server.Constants` classes. They're listed in alphabetical order. If you use Spring Boot, you should add the `vaadin.` prefix to them (e.g., change `brotli` to `vaadin.brotli`).
+The following table contains the properties that are defined in the [classname]`com.vaadin.server.DeploymentConfiguration`, [classname]`com.vaadin.flow.server.Constants` and [classname]`com.vaadin.flow.server.InitParameters` classes. They're listed in alphabetical order. If you use Spring Boot, you should add the `vaadin.` prefix to them (e.g., change `brotli` to `vaadin.brotli`).
 
-[cols="1,1,4"]
+[cols="1,1,4,1,1"]
 |===
-|Property Name |Default Value |Description
+|Property Name
+|System Property
+|Description
+|Default Value
+|Mode
+
 
 |`applicationIdentifier`
-|`default-project-id`
+|`vaadin.applicationIdentifier`
 |Application identifier that's generated by default based on the project build settings (e.g., Maven's `groupId` and `artifactId`, the string value is hashed and prefixed with `app-`) -- during a production build. The property is used only for the moment by the daily active users license model. It can be configured by developers to differentiate end-users distribution between the same applications running in a cluster -- ones that have the same group and artifact IDs.
+|`default-project-id`
+|DAU
 
 |`brotli`
-|`true`
+|`vaadin.brotli`
 |Determines whether pre-compressed https://github.com/google/brotli[Brotli] files should be used if accepted by the browser. Brotli files are created during a production build. The property is used only in production mode. Set to `false` if you want to serve uncompressed static resources.
+|`true`
+|Runtime
 
 |`closeIdleSessions`
-|`false`
+|`vaadin.closeIdleSessions`
 |Closes the Vaadin session if no UI is active. A UI is considered active if it's open on the client-side and has any activity -- besides heartbeat requests. By default, heartbeat requests keep the Vaadin session open even when there isn't any user interaction. Set to `true` to close idle sessions. See `heartbeatInterval` below.
+|`false`
+|Runtime
+
+|`devmode.componentTracker.enabled`
+|`vaadin.devmode.componentTracker.enabled`
+|Enable component tracking in development mode.
+|`true`
+|Dev
+
+|`devmode.devTools.enabled`
+|`vaadin.devmode.devTools.enabled`
+|Parameter for enabling dev tools. In production mode will always evaluate as `false`.
+|`true`
+|Dev
+
+|`devmode.frontendExtraFileExtensions`
+|`vaadin.devmode.frontendExtraFileExtensions`
+|Define additional frontend file extensions to copy from jar files to the application `frontend/generated/jar-resources`. Default extension copied are `.js`, `.js.map`, `.ts`, `.ts.map`, `.tsx`, `.tsx.map`, `.css` and `.css.map`.
+|``
+|Dev
 
 |`devmode.hostsAllowed`
-|`null`
+|`vaadin.devmode.hostsAllowed`
 |Defines the hosts allowed to access Vaadin development tools. A comma-separated list of allowed hosts should be provided as the value. The `?` and `*` wildcards can be used (e.g., `192.168.1.*,172.17.?.*`). Loopback addresses are always allowed, regardless of the value set here.
+|`null`
+|Dev
 
 |`devmode.liveReload.enabled`
-|`true`
+|`vaadin.devmode.liveReload.enabled`
 |Enables live reload. When using a server-side <<live-reload/index#, live reload tool>>, the browser is refreshed after code is rebuilt on the server. Set to `false` to disable automatic reloading of the browser. This applies only to development mode.
+|`true`
+|Dev
 
 |`devmode.optimizeBundle`
-|`false`
+|`vaadin.devmode.optimizeBundle`
 |Optimizes frontend resource bundles. All frontend resources in the classpath are included by default in the generated bundle in development mode. When set to `true`, the frontend build creates an optimized bundle by including only frontend resources that are used from the application entry points. It uses bytecode scanning, which increases application start-up time. Set to `false` to skip the optimization in production mode.
+|`false`
+|Dev
+
+|`devmode.output.pattern.timeout`
+|`vaadin.devmode.output.pattern.timeout`
+|Defines the time that we will wait for the frontend build tool to output either the success or error string for completion.
+|60000 ms
+|Dev
+
+|`devmode.remoteAddressHeader`
+|`vaadin.devmode.remoteAddressHeader`
+|The name of the custom HTTP header that contains the client IP address that is checked to allow access to the dev mode server. The HTTP header is supposed to contain a single address, and the HTTP request to have a single occurrence of the header. If not specified, remote address are read from the `X-Forwarded-For` header
+|
+|Dev
 
 |`devmode.sessionSerialization.enabled`
-|`false`
+|`vaadin.devmode.sessionSerialization.enabled`
 |Enables session serialization. When session serialization is enabled, [classname]`UI` instances and registered [classname]`StreamResource` instances are serialized or deserialized when restarting the development server. When set to `true`, for example, access control information can be preserved during development so that you don't need to log in for each change. This applies only to development mode.
+|`false`
+|Dev
 
 |`devmode.usageStatistics.enabled`
-|`true`
+|`vaadin.devmode.usageStatistics.enabled`
 |Enables Vaadin to collect usage statistics that can guide further development. Statistics are collected based on features that are used in the application. No data is collected in production mode. Some usage statistics are collected through the web browser. See the https://github.com/vaadin/vaadin-usage-statistics[client-side collector repository] for instructions on how to opt out. This applies only to development mode.
+|`true`
+|Dev
+
+|`devmode.vite.options`
+|`vaadin.devmode.vite.options`
+|Define extra options for VITE execution.
+|
+|Dev
 
 |`disable.automatic.servlet.registration`
-|`false`
+|`vaadin.disable.automatic.servlet.registration`
 |Disables automatic servlet registration that's required by Vaadin applications. You must register Vaadin servlets if set to `true`.
+|`false`
+|Runtime
 
 |`disable-xsrf-protection`
-|`false`
+|`vaadin.disable-xsrf-protection`
 |Disables cross-site request forgery protection. The protection is enabled by default. You should keep it enabled -- except for certain types of testing.
+|`false`
+|Runtime
 
 |`eagerServerLoad`
-|`false`
+|`vaadin.eagerServerLoad`
 |Enables the client-side bootstrap page to include the initial JSON data fragment.
+|`false`
+|Runtime
 
 |`enableErrorHandlerRedirect`
-|`false`
+|`vaadin.enableErrorHandlerRedirect`
 |If `{@code true}`, navigation error views implementing [interfacename]`HasErrorParameter` can be rendered for exceptions during RPC request handling.
+|`false`
+|Runtime
 
 |`frontend.hotdeploy`
+|`vaadin.frontend.hotdeploy`
+|Enables development using the frontend development server instead of an application bundle. This applies only to development mode. Hilla will always force frontend hotdeploy to true.
 |`false`
-|Enables development using the frontend development server instead of an application bundle. This applies only to development mode.
+|Dev
 
 |`heartbeatInterval`
-|300 seconds (i.e., 5 minutes)
+|`vaadin.heartbeatInterval`
 |Sets the heartbeat interval time. UIs that are open on the client-side send a regular heartbeat to the server indicating that they're still active even without ongoing user interaction. When the server doesn't receive a valid heartbeat from a given UI within a certain amount of time, it removes that UI from the session. The interval value is expressed in `seconds`. See also `closeIdleSessions`.
+|300 seconds (i.e., 5 minutes)
+|Runtime
 
 |`i18n.provider`
-|`null`
+|`vaadin.i18n.provider`
 |Sets the fully-qualified name for the internationalization provider class. To translate strings for localization, the application should implement the `I18NProvider` interface and define the class name in the `i18n.provider` property. See the <<{articles}/flow/advanced/i18n-localization#, Localization documentation>> for details.
+|`null`
+|Runtime
+
+|`launch-browser-delay`
+|`vaadin.launch-browser-delay`
+|Defines how long to wait before opening a new browser tab for the staring application. The time is counted always from the latest application start that would try to open a tab.
+|30 min
+|Dev
 
 |`maxMessageSuspendTimeout`
-|5000 ms (i.e., 5 seconds)
+|`vaadin.maxMessageSuspendTimeout`
 |Sets the maximum time in `milliseconds` that the client waits for predecessors of an out-of-sequence message, before considering them missing and requesting a full state resynchronization from the server. For example, when a server sends adjacent `XmlHttpRequest` responses and pushes messages over a low-bandwidth connection, the client may receive the messages out of sequence. Increase this value if your application experiences excessive resynchronization requests. However, be aware that it degrades the UX with flickering and loss of client-side-only states, such as scroll position.
+|5000 ms (i.e., 5 seconds)
+|Runtime
+
+|`menu.access.control`
+|`vaadin.menu.access.control`
+|Define a menu access control implmentation by giving a Fully Qualified Name to the control class.
+|
+|Runtime
+
+|`node.download.root`
+|`vaadin.node.download.root`
+|Base URL for downloading Node.js during build.
+|'https://nodejs.org/dist/'
+|Build
+
+|`node.version`
+|`vaadin.node.version`
+|Node.js version to get if one doesn't exist.
+|see FrontendTools.DEFAULT_NODE_VERSION
+|Build
+
+|`node.auto.update`
+|`vaadin.node.auto.update`
+|If true framework installed Node.js will be automatically updated to 'nodeVersion' if older version installed.
+|'true'
+|Build
 
 |`npm.excludeWebComponents`
-|false
+|`vaadin.npm.excludeWebComponents`
 |Excludes all Vaadin professional and core components from [filename]`package.json`. Material and Lumo themes are preserved. Excluded packages aren't installed by npm, which makes development bundles smaller. This property alone doesn't remove any Maven and Gradle dependencies. Supported also as a Vaadin Plugin property, `npmExcludeWebComponents`. See <<development-mode/index.adoc#exclude-vaadin-components, Optimize Bundle>> for more information.
+|'false'
+|Build
+
+|`npm.postinstallPackages`
+|`vaadin.npm.postinstallPackages`
+|Define postinstall scripts that need to be executes after npm install completes.
+|''
+|Build
 
 |`pnpm.enable`
-|`false`
+|`vaadin.pnpm.enable`
 |Enables `pnpm`, instead of `npm`, to resolve and download frontend dependencies. It's set by default to `false` since `npm` is used typically. Set it to `true` to enable `pnpm`. See <<development-mode/npm-pnpm-bun#, Switching Between npm, pnpm and bun>> for more information.
+|`false`
+|Build
 
-|`bun.enable`
+|`pnpm.global`
+|`vaadin.pnpm.global`
+|Force use of system installed pnpm instead of a Flow managed one.
 |`false`
-|Enables `bun`, instead of `npm`, to resolve and download frontend dependencies. It's set by default to `false` since `npm` is used typically. Set it to `true` to enable `bun`. See <<development-mode/npm-pnpm-bun#, Switching Between npm, pnpm and bun>> for more information.
+|Build
 
-|`productionMode`
+|`bun.enable`
+|`vaadin.bun.enable`
+|Enables `bun`, instead of `npm`, to resolve and download frontend dependencies. It's set by default to `false` since `npm` is used typically. Set it to `true` to enable `bun`. See <<development-mode/npm-pnpm-bun#, Switching Between npm, pnpm and bun>> for more information.
 |`false`
-|Sets the application to work in production mode. This disables most of the logged information to improve performance -- information that appears on the server and browser console. Development mode JavaScript functions aren't exported. Any `push` is given as a minified JavaScript file instead of a full-size one, and any static resources are cached. See the <<../production#,Deploying to Production>> for more information. Set to `true` when building applications for public deployment.
+|Build
+
+|`build.folder`
+|`vaadin.build.folder`
+|Build directory for application
+|`${project.build.directory}`
+|Build
 
 |`pushLongPollingSuspendTimeout`
-|`-1` (i.e., no timeout)
+|`vaadin.pushLongPollingSuspendTimeout`
 |Sets the timeout in `milliseconds` for network requests when using long polling transport. If you have long polling enabled with a proxy that has a timeout, set `pushLongPollingSuspendTimeout` to less time than the proxy timeout for clients to reconnect.
+|`-1` (i.e., no timeout)
+|Runtime
 
 |`pushMode`
-|`disabled`
+|`vaaddin.pushMode`
 |Enables server push. The permitted values are `disabled`, `manual`, and `automatic`. See <<{articles}/flow/advanced/server-push#, Server Push>> for more information.
+|`disabled`
+|Runtime
 
 |`pushServletMapping`
-|`""`
+|`vaadin.pushServletMapping`
 |Specifies the servlet mapping used for bidirectional (i.e., "push") client-server communication. Some Java application servers require special context. For example, you can specify websockets with this.
+|`""`
+|Runtime
 
 |`react.enable`
-|`true`
+|`vaadin.react.enable`
 |Whether to use React Router, add React core dependencies, React integration helpers and Vaadin's provided React components (i.e., `@vaadin/react-components`). Fallbacks to `vaadin-router`, excludes all React dependencies and adds `Lit` dependencies, if set to `false`. Vaadin plugin configuration for the `reactEnable` property needs to be set to match the configuration property value. See <<../../upgrading#hilla-react-dependencies, Hilla & React Dependencies>> for more information.
+|`true`
+|Runtime
 
 |`requestTiming`
-|`true` for development mode; `false` for production mode
+|`vaadin.requestTiming`
 |Includes basic timing information in responses that can be used for performance testing.
+|`true` for development mode; `false` for production mode
+|Runtime
+
+|`require.home.node`
+|`vaadin.require.home.node`
+|Force use of Vaadin installed Node.js instead of a globally installed Node.js version.
+|`false'
+|Build
 
 |`syncIdCheck`
-|`true`
+|`vaadin.syncIdCheck`
 |Enables synchronized ID checking. The synchronized ID is used to handle situations in which the client sends a message to a connector that has been removed from the server. It's set to `true`, by default. You should only disable it if your application doesn't need to stay synchronized, and suffers from a bad network connection.
+|`true`
+|Runtime
 
 |`webComponentDisconnect`
-|300 seconds (i.e., 5 minutes)
+|`vaadin.webComponentDisconnect`
 |Sets the number of `seconds` that a Vaadin Flow application embedded as a Web Component waits for a reconnect before removing the server-side component from memory.
+|300 seconds (i.e., 5 minutes)
+|Runtime
 
 |`sessionLockCheckStrategy`
-|assert
+|`vaadin.sessionLockCheckStrategy`
 |When production mode is enabled, the Vaadin session lock check is done according to this setting. By default, the check is done only if assertions are also enabled: this is to avoid the small performance impact of checking continuously the lock status. Alternative values are 'log' to log a warning, or 'throw' to fail with an `IllegalStateException`. The 'log' option also logs a full stack trace, enabling you to determine any problematic calls to Vaadin UI components from background threads. This is since Vaadin Flow version 24.4.
+|assert
+|Runtime
 |===
 
 
 == Vaadin Plugin Properties
 
 The following table contains the properties that are used only by the Vaadin Maven and Gradle Plugin, and are not applicable for deployment configuration:
 
-[cols="1,1,3,1"]
+[cols="1,1,4,1,1"]
 |===
-|System Property
 |Plugin Configuration
+|System Property
 |Description
 |Default Value
+|Mode
 
-|`vaadin.ci.build`
 |`ciBuild`
+|`vaadin.ci.build`
 |Determines whether `npm ci` is run, instead of `npm i`, for production frontend builds. If you use `pnpm` or `bun`, the install command runs with the `--frozen-lockfile` parameter. The build fails if the [filename]`package.json` and the lockfile have mismatching versions.
 |`false`
+|Build
 
-|`vaadin.force.production.build`
 |`forceProductionBuild`
+|`vaadin.force.production.build`
 |Forces Vaadin Flow to create a new production bundle, even if there is already a usable pre-compiled bundle. This is required usually when creating an optimized production bundle, and to load component sources to the browser on demand -- such as when opening a route where these components are used.
 |`false`
+|Build
+
+|`frontendDirectory`
+|
+|Directory containing the project's frontend files. Can be given as relative or absolute.
+|`./src/main/frontend`
+|Build
+
+|`generatedTsFolder`
+|
+|Directory where any generated frontend files should be put into. By default, the directory will be 'generated' and positioned below 'frontendDirectory'.
+|`null`
+|Build
+
+|`javaSourceFolder`
+|
+|Source folder used for component scanning during development mode.
+|`${project.basedir}/src/main/java`
+|Dev
+
+|`javaResourceFolder`
+|
+|Resources source folder used for component scanning during development mode.
+|`${project.basedir}/src/main/java`
+|Dev
+
+|`npmFolder`
+|
+|Directory containing 'package.json'.
+|`${project.basedir}`
+|Build
+
+|`openApiJsonFile`
+|
+|Defines where the OpenAPI json file is generated if required for exported services.
+|`${project.build.directory}/generated-resources/openapi.json`
+|Build
+
+|`projectBasedir`
+|
+|Directory containing 'pom.xml' or 'build.gradle'.
+|`${project.basedir}`
+|Build
+
+|`resourceOutputDirectory`
+|
+|Directory to place resources that are not served from the application.
+|`${project.build.outputDirectory}/META-INF/VAADIN/`
+|Build
+
+|`webpackOutputDirectory`
+|
+|Directory to generate served resources as 'index.js' and other generated files.
+|`${project.build.outputDirectory}/META-INF/VAADIN/webapp/`
+|Build
 
-|`vaadin.skip.dev.bundle`
 |`skipDevBundleRebuild`
+|`vaadin.skip.dev.bundle`
 |Prevents a frontend development bundle from being re-built, even if Vaadin Flow decides to use an existing compiled development bundle. This is mainly needed when re-bundling checker in Vaadin Flow has problems leading to false re-bundling, and one needs a workaround while it's being resolved.
 |`false`
+|Bundle
 
 |`vaadin.clean.build.frontend.files`
 |`cleanFrontendFiles`
 |Clears the generated frontend files after building a project for production. It keeps the generated files if they existed before the build, or if this parameter is set to `false`. When building a bundle in development mode, the generated files are removed unless they existed before the build.
 |`true`
+|Bunlde
 |===
 
 [discussion-id]`27BF72FB-1E23-42B0-B540-A602F9AD4571`