Vaadin 14.5.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.5 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.5.2)
- Fixes:
-
⧉ Force pnpm version <= 5. PR:10576. Ticket:10571
pnpm >= 6.0.0 requires at least Node.js v12.17. This requirement may not be satisfied as framework current accepts Node.js 10. pnpm 6.0 can be used with newer Node.js versions if the versions check is disabled with vaadin.ignoreVersionChecks=true. But in pnpm 6 the pnpmfile.js is renamed to .pnpmfile.js and thus the Flow generated pnpmfile.js will not be used by pnpm - meaning that versions are not locked.
-
⧉ Consider first added route as main route and always return it first (#10556). PR:10568. Ticket:10528
-
⧉ Provide info on file name when Json parsing fails (#10423). PR:10548. Ticket:10323
Adds the package file name to exception message in case of JsonException in order to provide clean explanation where to look into. (cherry picked from commit 1ea4ceffefc8f364261abea7f3d925c9f31e94a6)
-
⧉ Don't use ErrorHandler for IOExceptions in StreamReceiverHandler. PR:10553. Ticket:10351
-
⧉ Use getContentLengthLong instead getContentLength (#10506). PR:10540. Ticket:10392
Use Servlet 3.1 ServletRequest::getContentLengthLong to get the content size as a long value for the big files upload, because getContentLength may return -1 (file size is bigger than int capacity).
-
⧉ Allow spaces between html function call and back tick. PR:10523. Ticket:8881
-
⧉ Use warn instead of trace for WC exporters discovering. PR:10507. Ticket:9855
-
⧉ Do lazy initialization in a thread-safe way (#10456). PR:10461. Ticket:9323
-
⧉ Make shortcuts not break writing on inputs. Ticket:10362
Only passes the delegated event forward when it maps to the shortcut key. For the shortcut key, preventDefault() is the default behavior and default can be allowed with allowBrowserDefault() in the ShortcutRegistration.
-
Components
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:
- 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).
- Issues that are not component-specific (e.g. requests for new components) or encompass multiple components should be posted in vaadin-flow-components repository.
- 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
- If you encounter an issue with Designer, the repository is https://github.com/vaadin/designer
- If you encounter an issue with TestBench, the repository is https://github.com/vaadin/testbench