Vaadin Flow 2.5.0.alpha1
Flow 2.5 is a minor release targeted to Vaadin 14.5.
2.5.0.alpha1 has all the same fixes as 2.4.6, and additionally:
-
Breaking Changes:
-
⧉ Support current pnpm versions. PR:9848
If you are using pnpm (instead of default npm), starting from version 2.5 the Flow build will automatically update the pnpm to a newer version. In case you've installed the pnpm version manually on your system and the automatic update fails, the build will fail with a clear message telling you to update to a newer version of pnpm.
- Supported version of
pnpm
is upgraded to5.0
(previously was4.4
) - Default
pnpm
version is upgraded to5.15.1
(previously was4.5.0
)
Remove
pnpm-lock.yaml
whenpackage.json
dependencies are updated to work around pnpm/pnpm#2587. Invokepnpm
vianpx
instead of relying on global installation or installing into~/.vaadin/node_modules
. - Supported version of
-
⧉ Make VaadinService.dependencyFilters unmodifiable
While the change is backwards compatible from API perspective, it could be considered a behavior change although there is quite low risk of exposure in apps. Thus targeting 2.5 for the LTS and the recently released 5.0.
-
-
New Features:
-
⧉ Add HasOrderedComponents in HTML layout elements. PR:9734
Closes #8188 This PR implements HasOrderedComponents for all common HTML layout elements: - Aside - Article - Div - Footer - Header - Main - Nav - Section The test is created in the base test class to simplify the unit testing of all components. To make sure that the interface isn't removed by accident, every class implements the test explicitly and fails if the interface is removed.
-
⧉ Implement NativeDetails as html component. PR:9735
NativeDetails is based on vaadin-details except that the html property is called open instead of opened and the event is called Toggle like the html dom event. To reduce the API noise
NativeDetails
extendsHtmlComponent
instead ofHtmlContainer
.HasText
andHasComponents
would interfere with the already set<summary>
inside the<details>
. -
⧉ Add support for Range header to StaticFileServer. PR:9154. Ticket:9083
A Range header can specify either a single byte range, e.g.
Range: bytes=0-99
, or multiple ranges, e.g.Range: bytes=0-99, 200-299
. The ranges do not need to be sequential and can have overlap; e.g. Range: bytes=200-299, 0-219 is valid; such requests will open a new stream reading from the beginning of the file for each out-of-order range. The motivation for this feature is to support video playback on Safari.
-