Vaadin Flow 2.7.0.beta1
Changes in Flow from 2.7.0.alpha2
-
Breaking Changes:
-
Fixes:
-
⧉ Filter vaadin-core from versions pinning (#11027) (#11037). PR:11598. Ticket:11025
-
⧉ Fix build issue with npm 7.20.3+. PR:11588
Add
babel-loader
to devDependencies to fix issue happening after npm 7.20.3 where the loader gets only installed into a sub node_modules folder and not to root. Closes #11584 -
⧉ Pin platform trans. deps with npm CP: #10864. PR:11567. Ticket:10572
Uses the same vaadin_versions.json file based pinning as with pnpm. In case the application has @NpmPackage annotation with a certain version, then that is used over the platform pinned version. When that is older, a warning is logged (like with pnpm). In case a dependency has been pinned directly in package.json, then that is used over the platform pinned version. When that is older, a warning is logged (like with pnpm).
-
⧉ Don't fire shortcut event if ancestor of component is not visible (#11565). PR:11581. Ticket:7033
-
⧉ Clean up managed default versions. PR:11563. Ticket:11561
Clean up default dependencies and devDependencies if they have changed.
-
⧉ Fail-fast if the path to npm cache contains whitespaces. PR:11539
Checks that the npm version accepts whitespaces in user home path and explains how to fix that otherwise.
-
⧉ Only copy javascript files.. PR:11562
When copygin the webcomponentsjs polyfill do not copy in package.json or the md files. closes #11560
-
⧉ Register data provider listener only if it has not been registered
(cherry picked from commit 067f63f)
-
⧉ Correct comment in webpack config file. PR:10475. Ticket:8485
-
⧉ Set Vaadin session attribute using lock (#11538). PR:11542. Ticket:11519
-
⧉ Use byte[] instead of String to store stats.json. PR:11529. Ticket:11515
This is made to avoid excessive memory usage when managing the data
-