Vaadin 14.3.1

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.2 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.

Framework

• Store scroll position in state when entering route not found view (vaadin/flow#8693)
• Fall back to user.dir / cwd as frontend build base directory only if a project directory (vaadin/flow#8249, vaadin/flow#8403)
• More flexible npm proxy regex (vaadin/flow#8703)
• Fix priority order of npmrc files (vaadin/flow#8701)

Components

• Confirm Dialog: use confirm dialog web component 1.2.1

Changes since 14.3.0

• Vaadin Flow (2.3.1)
• Vaadin Multiplatform Runtime (Prime) for Framework 7 (2.0.4)
• Vaadin Multiplatform Runtime (Prime) for Framework 8 (2.0.4)
• Vaadin Confirm Dialog (PRO) (Flow integration 2.1.1, web component v1.2.1)

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.

Known Issues and Limitations

Flow

Components

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. If you encounter an issue when using the HTML/JS API of a component or the component renders incorrectly, the problem is likely in the web component. The web component repositories are named like https://github.com/vaadin/vaadin-button
2. If you encounter an issue when using the Java API of a component, the problem is likely in the Flow integration of the web component. The Flow component integration repositories are named like https://github.com/vaadin/vaadin-button-flow
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