Closed manolo closed 1 year ago
Still reproduces with the latest Flow 24.0-SNAPSHOT
.
Polymer dependencies were used in V23.3 for IronList
and have been removed in V24 in https://github.com/vaadin/platform/pull/3430 .
Web components don't have a vaadin-
prefix anymore in V24, thus Flow thinks that they are new components.
But this shouldn't affect, because Flow calculates dependencies in memory for package.json taking into account specified platform version.
Then probably we need some kind of white list for these components, so as it's safe still to use the bundle
The solution seems more simple: we can exclude all the entries from dependencies
that have same package name and version as in dependencies
inside vaadin
block. So everything that is not defined by developer but by Vaadin will be removed and then re-added back but with the actually used platform version.
Description of the bug
If I have an 23.3 application that has no component customisations, it should not run
npm install
nor generate a newdev-bundle
but use the one shipped in the platform.Seems similar to https://github.com/vaadin/flow/issues/15907
Workaround
Removing
package.json
orpackage-lock.json
it worksExpected behavior
Don't generate any bundle
Minimal reproducible example
This is the output in console
Versions