Vaadin 19.0.4
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 19.0 in GitHub releases, including new features, getting started, supported browsers and other technologies, and migration notes.
Visit vaadin.com to get started.
New and Noteworthy
Here are the highlighted new and improved features in this maintenance release.
Vaadin Flow (6.0.5)
- Fixes:
-
⧉ Store spring csrf to bootstrap page. PR:10577
Stores spring CSRF token into meta tags into the bootstrap page, which is used for
login()andlogout()helpers. It has the benefit that login and logout are now Spring CSRF protected, we no longer need to ingore Spring CSRF protection for login likehttp.csrf().ignoringAntMatchers("/login"); -
⧉ Force pnpm version <= 5 (#10576). PR:10587. 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.cjs 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:10566. Ticket:10528
-
⧉ Don't use ErrorHandler for IOExceptions in StreamReceiverHandler. PR:10553. Ticket:10351
-
⧉ Use getContentLengthLong instead getContentLength (#10506). PR:10538. 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).
-
⧉ Provide info on file name when Json parsing fails. PR:10423. Ticket:10323
Adds the package file name to exception message in case of JsonException in order to provide clean explanation where to look into.
-
⧉ Allow spaces between html function call and back tick. PR:10523. Ticket:8881
-
Components
Changes in vaadin-dialog-flow
Changes in vaadin-grid-flow
Changes in vaadin-radio-button-flow
- Fixes:
Support
vaadin 19 is supported for one month after Vaadin 20 has been released. The latest LTS (long term support) version is Vaadin 14. More details of our release model are available on our roadmap page.
Vaadin also provides commercial support and warranty.
Getting Started with Vaadin
App starters
The best way to get started with Vaadin is to go to https://start.vaadin.com and configure your new application by setting up your views, entities, styles, and 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