Leif Åstrand

> Just one thing to point out, to ensure it still works: Create a Project that uses Free Components + a single Pro Component (like Charts) -> so it's possible...

This ticket describes a broad vision based on introducing some new principles: 1. Make the common cases easy: There's a small set of getting-started cases that we want to optimize...

I'm not aware of applications getting broken if we limit the change to applications that use Spring Boot. It is true that the development setup for the application becomes bigger...

We have indeed considered the option of releasing these changes as Vaadin 25.0.0 instead of Vaadin 24.4.0 but concluded that it would be redundant since we aren't removing any functionality....

My impression is that we got all the desperately needed adjustments done already for 24.4 and what remains is more in the "maybe for the next major version or maybe...

The reason why it works this way is that when a component instance is attached to the component tree, imports are added based on `@HtmlImport` annotations on the component class....

> Wouldn't it be more consistent, if the `@Id` annotation wouldn't trigger imports? That wouldn't work in cases like `Grid` where an additional `gridConnector.js` also needs to be included to...

Should be fixed by https://github.com/vaadin/hummingbird/issues/1344

That improved performance isn't super relevant for headers since you have a fixed number of those and they typically remain the same while the user interacts with the application. The...

One additional thing to keep in mind is that the additional paths might or might not be based on the same view class. In other words, there are two different...