Changes since 25.0.0-beta8
Breaking changes
-
Install Node.js in version-specific directories
Commit · Pull request- Install Node.js to version-specific directories (e.g., node-v24.10.0/) instead of a single node/ directory to support multiple versions - Add fallback logic to use existing compatible Node.js installation when the requested version is not available Add ActiveNodeInstallation record to cache the node executable path and version. This ensures node lookup happens only once and the same location is used throughout the build process. The node.auto.update configuration option is no longer meaningful with version-specific installation folders. Previously, this setting controlled whether to update an existing Node installation in-place when a newer version was available. With versioned folders (e.g.,
/.vaadin/node-v24.10.0/), each version is installed in its own directory, so there is no "update" operation - the requested version is simply installed to its own folder. Removed support for a/.vaadin) with versioned pathsnodefolder in the project Node.js is now only looked up in: - Global PATH (if version is supported) - Alternative directory (
- Install Node.js to version-specific directories (e.g., node-v24.10.0/) instead of a single node/ directory to support multiple versions - Add fallback logic to use existing compatible Node.js installation when the requested version is not available Add ActiveNodeInstallation record to cache the node executable path and version. This ensures node lookup happens only once and the same location is used throughout the build process. The node.auto.update configuration option is no longer meaningful with version-specific installation folders. Previously, this setting controlled whether to update an existing Node installation in-place when a newer version was available. With versioned folders (e.g.,
New features
- Add ReferenceSignal
Commit · Pull request · Issue - Add Signal.not
Commit · Pull request
Fixes
-
Use file watcher and inline stylesheets for hot reload
Commit · Pull request · Issue -
Fix npm relative folder and tests
Commit · Pull request- Fix relative path for npm-cli in windows - Validate found alternative node. - Remove validate npm as the faulty version 6.0 should never be installed.
-
Remove use of commons-io in dev-server
Commit · Pull request · IssueRemove the usage of commons-io in vaadin-dev-server module as it is not required and has been comming from transitive dependency.
-
Make deny layout more descriptive.
Commit · Pull requestHave the deny and log be more descriptive on which view and which layout denies navigation due to access rules. Closes #21956
-
Make buildFrontend exclude dev deps
Commit · Pull request · IssueExclude vaadin-dev, vaadin-dev-server, vaadin-dev-bundle, copilot, flow-archive-extractor, ui-tests, gentyref, and atmosphere-runtime from the buildFrontend mojo by default. In addition, excludes com.vaadin.external.gw, com.vaadin.servletdetector, and open by default even without custom frontendScanner configuration.