2.1.0.beta1 - Prerelease
Pre-release
Pre-release
Vaadin Flow 2.1.0.beta1 is a prerelease of Vaadin Flow 2.1.0
Vaadin Flow 2.1.0.beta1
Flow is a new Java web framework for creating UIs using Java or HTML. Flow handles everything related to communication between client and server and makes it possible to create UIs using the desired abstraction level you choose. It has all the capabilities you need to build a modern web app: from high level APIs for structuring your applications and binding data to it, into taking full control over the DOM and communication with HTML templates.
Flow is a part of the Vaadin platform. For information and helpful resources like documentation and examples on Vaadin Flow, please visit the Flow page vaadin.com/flow.
The complete documentation can be found here
New features in beta1:
- Embedding support for @PreserveOnRefresh (#639)
- Exported web components should not be based on Polymer (#5800)
Bugfixes in beta1 (since alpha1):
- Webpack-dev-server re-runs on each java modification (#6277
- Flow fails to serve static resources from latest webjars (#6241)
- Frontend resources import with multimodule Maven projects (#6306)
- Load order guarantee of @javascript (broken) and @jsmodule annotations (#6198)
- Reverse the reversed error message (#6290)
- Allow running dev mode without flow-build-info.json if cwd points to a valid project directory (#6233)
- Add log for failing path relativization (#6410)
- Fail for non existing folders in dev mode. (#6405)
- Don't store parent registry in session route registry. (#6389)
- Set response status based on server handling logic status. (#6381)
- npm install is not run if generated package.json content has not changed (#6385)
- Fix style overrides when placing imports on RouterLayouts (#6423)
- Hash only for dependencies in package.json (#6422)
- Fix getting shrinkwrap version from package-lock.json (#6433)
- Show a warning when @HtmlImport is used in npm mode (#6417)
- Fix DomEventListener filter (and other stuff) removal (#6427)