github vaadin/platform 25.4.0-beta1
Vaadin 25.4.0-beta1

pre-release33 minutes ago

Upgrading · Docs · Get Started

This is a pre-release for the Vaadin 25.4. We appreciate if you give it a try and report any issues you notice.

New and Noteworthy Since Vaadin 25.3

Platform

  • Content Security Policy ready: Flow can now send a nonce-based Content-Security-Policy header and run without unsafe-eval. Set vaadin.csp=warn to log every call in your application that would break under a strict policy, then switch to strict. Server-initiated JavaScript, event data, filters, shortcuts and Flow's own client code now run from the bundle instead of eval. (📖 Docs)
  • Switch and Breadcrumbs are production ready: both components no longer need a feature flag.
  • Leaner Spring dependencies: vaadin-spring no longer brings Spring MVC, Spring WebSocket or Hibernate Validator to your classpath. The Vaadin Spring Boot starter adds the websocket and validation starters, so Spring Boot apps keep working as before. Plain Spring apps must declare these dependencies themselves.
  • CDI add-on and Quarkus extension follow the Flow version: they are now developed in the Flow repository and versioned as 25.4.x. Their group and artifact IDs are unchanged.
  • Node.js 26 is now the minimum supported version. If your global Node.js is older, Vaadin downloads Node.js 26 into ~/.vaadin.
  • SpringBoot 4.2 is the supported version in this Vaadin minor.

Flow

  • Strict CSP and declared JavaScript: JavaScript can be declared in Java interfaces with @JsDefinition and @JsExpression, bundled at build time and called by id. Calls return typed JavaScriptResult<T> values. addEventDataPath() replaces the string-based event data API, which is now deprecated.
  • New HTML components: NativeForm for native <form> elements, such as login forms that work with password managers. Video, Audio and Source for the browser's media players, served from a URL or a DownloadHandler. (📖 Docs)
  • Downloads from any component: Download.onClick() starts a download when any component is clicked, and OpenInNewTab.onClick() opens a URL or handler content in a new tab, with no Anchor needed. File handlers support HTTP range requests, so media players can seek and downloads can resume. A UI stays alive while its upload or download is still running. (📖 Docs)
  • Hierarchical menus: @Menu(parent = ...) and MenuConfiguration.getMenuEntriesTree() build nested navigation menus from your routes.
  • Lifecycle events: the service event bus now reports the start and end of every request and navigation, with outcome, duration and handler. Client-side vaadin-request and vaadin-server-message events let page scripts measure round trips. Observability Kit uses these events.
  • Spring Security: VaadinSecurityConfigurer can choose the URL to go to after login, handle login failures, map Keycloak roles to Spring authorities, and handle expired sessions so that the client understands the response. Multiple @EnableVaadin annotations are now merged.
  • CSS cascade layers and runtime ES modules: @StyleSheet(layer = "...") loads a stylesheet into a cascade layer, so its rules always lose to your own styles. @JavaScript(type = MODULE) loads an ES module at runtime without bundling it. (📖 Docs)
  • Also: null-safe converter helpers in Binder, Component.findAncestor(predicate), the browser time zone in ExtendedClientDetails, RouteConfiguration.getUrl() with query parameters, and a redesigned default PWA offline page.

Hilla

  • TypeScript generated in Java: endpoint and model TypeScript is now generated by Java in the same run that scans your classes, with no Node.js process. Builds no longer need Node.js for this step. TypeScriptProcessor lets build tools run the generation themselves. Breaking: the generator plugin configuration, the nodeCommand option and hilla-openapi.json are removed.
  • New form models: generated form models are now @vaadin/hilla-models constants, and the legacy class-based lit-form models are removed. The new builders m.record, m.literal and m.lazy describe maps, literal values and circular references between models.
  • JSpecify @NullMarked packages are treated as non-null by default, like Spring's @NonNullApi. (📖 Docs)
  • Also: Swagger, Jackson 2, SnakeYAML and gentyref are no longer transitive dependencies, and many generator fixes for Kotlin properties, generic parameters and unusual property names.

Design System

New components

  • PDF Viewer (Pro): 🔬 Preview. Shows PDF documents inside your application, with page navigation, zoom and a toolbar. Tagged PDFs expose their structure to screen readers. Enable it with the pdfViewerComponent feature flag.

New in existing components

  • Labels aside: a LABEL_ASIDE theme variant puts a field's label next to the input instead of above it. It works for text fields, combo boxes, pickers, select, checkbox and radio groups, custom field and slider. Form Layout gets a label text alignment setting.
  • Multi-Select Combo Box: a "Select all" button that selects or deselects all items, or all filtered items.
  • Text Field: select text or move the cursor from the server with setSelectionRange(), selectAll() and setCursorPosition().
  • Button: start a file download on click with setDownloadHandler(). Context Menu and Menu Bar items can start downloads too. DisableOnClickMode.UNTIL_RESPONSE re-enables the button automatically after the server has handled the click.
  • Grid: select a row by clicking anywhere on it in multi-select mode, getColumnBySortProperty(), and context menu content that knows the clicked column.
  • Also: look up the context menus attached to a component, TabSheet.findTabContaining() and removeAll(), Notification.getText(), camera capture in Upload, Map icons sized in pixels, Slider theme variants, submitDisabled in Message Input and AI chat while a request or upload is running, and AI Grid paging through your DatabaseProvider.

Accessibility

  • Heading levels for Dialog, Confirm Dialog and Card titles. Dialog supports aria-describedby. Select is announced as a combobox. Date Picker calendar dates work better with VoiceOver and NVDA.

Breaking changes

  • The web component i18n property is undefined until you set it. A slotted Card title now wins over cardTitle. Date Picker calendar cells and Grid body cells have a new DOM, which may affect custom CSS and tests. Two-way signal bindings now require a write callback. See the upgrade guide.

Copilot

See the Vaadin Copilot documentation.

  • Added an updated onboarding flow that guides users into identification.
  • Added a redesigned sign-in dialog that supports signing in through the license checker.
  • Added support for generating Browserless tests from the UI test recorder.
  • Improved Kotlin views to honor the API-selection dialog.
  • Added support for copying a component from a Kotlin view.
  • Added experimental optimistic updates to make edit mode feel more responsive.

Testing

  • Find elements by test ID in TestBench with withTestId() and testId().
  • Browserless tests: reload() simulates a browser reload. New testers for UploadButton, UploadDropZone and UploadFileList can simulate failed and aborted uploads. roundTrip() runs pending UI.access() tasks. Each window gets its own UI. Lookup failure messages name the query conditions.
  • TestBench elements: read Grid cells in bulk, GridSorterElement, the Multi-Select Combo Box "Select all" button, and PdfViewerElement.

Observability Kit (Pro)

  • Browser interaction timing now works in production and with WebSocket push. Navigation, request and session lock metrics are measured from Flow's new lifecycle events, so they are more accurate.

Changelogs

Official add-ons and plugins:

Supported technologies

Desktop browser
  • Chrome (evergreen).
  • Firefox (evergreen).
    • Firefox Extended Support Release (ESR). Note that Vaadin 25 doesn't support Firefox ESR 115.
  • Safari 17 or newer (latest minor version in each major series).
  • Edge (Chromium, evergreen).
Mobile browser
  • Chrome (evergreen) for Android (4.4 or newer).
  • Safari 17 for iOS or newer (latest minor version in each major series).
Development OS
  • Windows
  • macOS
  • Linux
IDE

Any IDE or editor that works with the language of your choice should work well. Our teams often use IntelliJ, Eclipse, VS Code among others.

Vaadin IDE plugins (IntelliJ and VS Code) support the IDE versions released during the last 12 months

Vaadin Designer supports the following IDEs:

  • Eclipse from Photon and upwards

  • JetBrains IntelliJ IDEA from 2017 upwards

Java Version 21 of any JDK or JRE
Maven Version 3.8 or newer
Gradle Version 8.14 or newer
Application server

Vaadin Flow requires Java Servlet API 6.1 and Java 21 or newer. It is tested on:

  • Apache Tomcat 11

  • Open Liberty 23

  • RedHat JBoss EAP 8.1

    • To work with RedHat JBoss EAP 8.0, the following content needs to be added under WEB-INF folder as jboss-deployment-structure.xml
    Workaround for supporting RedHat JBoss EAP 8.0
     <jboss-deployment-structure>
       <deployment>
         <exclude-subsystems>
           <subsystem name="jaxrs" />
         </exclude-subsystems>
       </deployment>
     </jboss-deployment-structure>
  • WildFly 36 +

    • Latest WildFly versions are still using Jackson 2, in order to work with Vaadin 25, the following content needs to be added under WEB-INF folder as jboss-deployment-structure.xml
    Workaround for supporting WildFly 36
     <jboss-deployment-structure>
       <deployment>
         <exclude-subsystems>
           <subsystem name="jaxrs" />
         </exclude-subsystems>
       </deployment>
     </jboss-deployment-structure>
    Workaround for supporting WildFly 37+
     <jboss-deployment-structure>
       <deployment>
         <exclusions>
             <module name="com.fasterxml.jackson.core.jackson-annotations"/>
         </exclusions>
       </deployment>
     </jboss-deployment-structure>
  • Jetty 12

  • Payara Server 6

  • Payara Micro 6

Node.js Version 26.x
NPM Version 11.3 or newer
PNPM Version 10.16 or newer
Spring Boot Version 4.2

Don't miss a new platform release

NewReleases is sending notifications on new releases.