Vaadin 14.6.2

Vaadin consists of a set of web components, a Java web framework, configurable themes, tools and a set of app templates.

This is a maintenance release of Vaadin.
See the full release notes for Vaadin 14.6 in GitHub releases, including new features, getting started, supported browsers and other technologies, and migration notes.

Visit vaadin.com to get started.

Support

Vaadin 14 is an LTS (long term support) version, which will be supported for 5 years after the GA (general availability) release. More details of our release model are available on our roadmap page.

Vaadin also provides commercial support and warranty.

New and Noteworthy

Here are the highlighted new and improved features in this maintenance release.

Vaadin Flow (2.6.2)

Changes in Flow from 2.6.1

• Fixes:

  • ⧉ Set routes first into the template (#11107). PR:11128.

  • ⧉ Don't serve directories as static files (#11072). PR:11122

    Add check to the resource to see if it is a directory and do not serve if this is the case. Fixe #11047 # Conflicts: # flow-server/src/main/java/com/vaadin/flow/server/StaticFileServer.java

  • ⧉ Prevent passing bad character to wp (#11099). PR:11116

    The webpack dev-server does not escape " character, as it is not valid URL. This limitation was not checked when passing request to it via DevModeHandlerImpl.

  • ⧉ Annotate default error handlers. (#11063) (#11089). PR:11092

    Annotate default error handlers with the new annotaton DefaultErrorHandler so that we can also in add-ons have default handlers that can be overridden by user handlers. Part of vaadin/spring#661

  • ⧉ Use x64 version for mac for old nodejs (#11065). PR:11070. Ticket:11060

    Use the x64 package for mac if the installed node version is < 16.0.0 as ARM package is not available before this.

  • ⧉ Using a custom RouteRegistry (#11033) (#11055) (CP: 2.6). PR:11058. Ticket:11022

    Make it possible to create a custom RouteRegistry and add test module for it.

  • ⧉ Fix external url reference (#11039). PR:11061. Ticket:11015

    flow-frontend is copied directly to node_modules making css-loader try to resolve urls for files that shouldn't be resolved.

  • ⧉ Don't update cached extended details inside callback (#11043). PR:11051. Ticket:473

    Makes fetching extended client details work for Multiplatform Runtime.

  • ⧉ Remove old router layouts content before navigation. PR:10973. Ticket:345

    Recursively removes content of the all nested router layouts of the given old content when the navigation occurs. This is needed to let Dependency Injection frameworks (Spring and CDI add-ons) to re-create managed components with no duplicates/leftovers. (cherry picked from commit 5f5fdcd1754bd283ba3f787d3d4dee0ca57955de)

  • ⧉ Change construct-style-sheets-polyfill to be a runtime dependency (#10991) (#10996). PR:11006. Ticket:10988

  • ⧉ Update the used Opcode from 7 to 8 (#10979). PR:10986. Ticket:10870

    Update used ClassVisitor ASM version from 7 to 8 to support Java16 record

Components 14.6.2

Changes in vaadin-checkbox-flow

• Fixes:
  • ⧉ Disable checkbox after applying value (#994). PR:1715. Ticket:993

Changes in vaadin-date-picker-flow

• Warranty Fixes:

  • ⧉ Update date picker overlay after setting I18N settings (#1742) (CP: 14.6). PR:1761. Tickets:1411

    (cherry picked from commit ec6054541b6fe1df6d40b044dc89059a9d3edbb2)

Changes in vaadin-grid-flow

• Fixes:
  • ⧉ Check if connector is available. PR:1739

Getting Started with Vaadin 14

App starters

The best way to get started with Vaadin 14 is to go to https://vaadin.com/start and pick an app template for the technology stack you’re interested in.

For the full list of how to get started go to the GitHub releases.

Reporting Issues

We appreciate if you try to find the most relevant repository to report the issue in. If it is not obvious which project to add issues to, you are always welcome to report any issue at https://github.com/vaadin/platform/issues.

A few rules of thumb will help you and us in finding the correct repository for the issue:

1. Bug tickets and enhancement requests that are specific to a certain Vaadin component should be posted in the component's Web Component repostory (e.g. https://github.com/vaadin/vaadin-button for Button).
2. Issues that are not component-specific (e.g. requests for new components) or encompass multiple components should be posted in vaadin-flow-components repository.
3. If you encounter an issue with Flow which does not seem to be related to a specific component, the problem is likely in Flow itself. The Flow repository is https://github.com/vaadin/flow
4. If you encounter an issue with Designer, the repository is https://github.com/vaadin/designer
5. If you encounter an issue with TestBench, the repository is https://github.com/vaadin/testbench