github vaadin/platform 16.0.0.beta2
Vaadin 16.0.0.beta2
on GitHub

latest releases: 24.4.0.alpha25, 23.3.34, 24.4.0.alpha24...
pre-release3 years ago

Vaadin 16.0.0.beta2

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

Visit vaadin.com to get started.

New and Noteworthy

Here are the highlighted new and improved features in Vaadin 16. To see the full list of bug fixes and improvements, check Included Projects and Change Log.

Automatic Node installation

  • Available from Vaadin versions 16
  • If no global or local Node installation is found Node will be automatically installed to ~/.vaadin
    • Only requires the first project to install as later can use the same installation
    • No need to have Node installed globally for CI
  • Uses proxy data from
    • System properties
    • {project}/.npmrc
    • ~/.npmrc
    • Environment variables

pnpm is the default frontend package manager

  • Now pnpm is used by default instead of npm
    • npm was still default in Vaadin 14.2 and 15
  • No migration needed - pnpm is installed once to /.vaadin inside home folder. See differences here for more information about what has changed

Devmode is run as a separate thread to speed up server startup

  • Allows server to continue startup parallel to Flow development mode process which runs pnpm/npm and webpack build
  • The browser shows a white page that is automatically refreshed to open app once devmode process has finished
  • As server is started up faster, there is no timeout from "run from IDE" or from server plugins

RTL Language Support

All components have full support for right-to-left languages (e.g. arabic, hebrew) so that they render correctly when the UI is in RTL mode.

Hierarchy column renderer

Component renderer can be used in TreeGrid hierarchy column.

Grid hidden columns performance fix

Hidden columns are no longer rendered to the DOM, which improves Grid/TreeGrid/GridPro performance with a large number of hidden columns.

Components

  • New component: Vaadin DateTimePicker
  • Draggable, Resizable and Modal configuration for Dialog
  • vaadin-ordered-layout: support for more flexbox features in FlexLayout and Scroller for scrolling overflowing content
  • vaadin-time-picker: New max and min time API

Changes since 16.0.0.beta1

Flow 3.1.0.beta 2

Notable changes since 3.1.0.beta1

  • Verbose output for webpack bundling progress is now disabled for production builds
  • Updated Router version
  • Fixes flow-build-info.json referencing local machine directories in production builds
  • Fixed missing npm install when there are frontend changes pulled from version control to the project

All changes since 3.1.0.beta1
All changes since 3.0

Please refer to Beta 1 Prerelease for Vaadin 16 for a complete list of features, issue and limitations.

Vaadin TestBench 6.2.2 (Pro)

Vaadin TestBench is a tool for creating and running browser based integration tests for your Vaadin application. TestBench simulates a user of your application, performs the tasks specified using Java code and verifies that the expected actions take place in the application.

Changes since Version 6.2.1

  • Update to latest parent and LC
    Uses Selenium 3.141.59

Changes since 16.0.0.beta1

Support

Vaadin 16 is supported for one month after Vaadin 17 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.

Included Projects and Change Log

Vaadin includes the following projects. Release notes with detailed change logs for each project are linked below.

Projects marked as (Pro) are available for users with Pro or Prime subscriptions. Everything else is free and open source.

Java Web Framework

Components

Themes

  • Vaadin Lumo theme (v1.6.0)
  • Vaadin Material theme (v1.3.2).

Router

Tools

Getting Started with Vaadin

App starters

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

Manually changing Vaadin version for Java projects

Add the following contents to your project pom.xml. 

<dependencyManagement>
    ...
    <dependency>
        <groupId>com.vaadin</groupId>
        <artifactId>vaadin-bom</artifactId>
        <version>16.0.0.beta2</version>
        <type>pom</type>
        <scope>import</scope>
    </dependency>
    ...
</dependencyManagement>

<repositories>
    <repository>
        <id>vaadin-prereleases</id>
        <url>https://maven.vaadin.com/vaadin-prereleases</url>
    </repository>
</repositories>

<pluginRepositories>
    <pluginRepository>
        <id>vaadin-prereleases</id>
        <url>https://maven.vaadin.com/vaadin-prereleases</url>
    </pluginRepository>
</pluginRepositories>

Known Issues and Limitations

This is the prerelease version of Vaadin 16 for evaluating a number of new features and bug fixes. The API in this prerelease version is not considered final and may change based on user feedback.

Flow

  • The Template-in-Template feature has some limitations
  • Links matching the context do not result in browser page load by default, instead they are handled with application routing. To opt-out, set the router-ignore attribute on the anchor element. This opt-out is needed for cases when native browser navigation is necessary, e. g., when using Anchor to link a StreamResource download.

Migrating from Vaadin 8

See the migration guide

Migrating from Vaadin 10-14

See the migration guide

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
Check out latest releases or
releases around vaadin/platform 16.0.0.beta2

Don't miss a new platform release

NewReleases is sending notifications on new releases.

Get notifications