vaadin/flow 6.0.8

Vaadin Flow 6.0.8

on GitHub

Vaadin Flow 6.0.8

Changes in Flow from 6.0.7

• Fixes:

  • ⧉ Upgrade to LitElement 2.5.1 and lit-html 1.4.1 (#10912). PR:10919

  • ⧉ Watch component folders in parent themes (#10834). PR:10883. Ticket:9948

    Adds parent themes component folders to be watched by webpack.

  • ⧉ Upgrade to LitElement 2.5.0 and lit-html 1.4.0 (#10874) (CP: 6.0). PR:10879. Ticket:10826

  • ⧉ Preserve internal JS UI state properly (#10823) (CP: 6.0). PR:10838. Ticket:10757

  • ⧉ Use global node and tools if they are available first (#10753). PR:10769. Ticket:9863

  • ⧉ Warn to delete component CSS with theme generated in one run (#10779). PR:10828. Ticket:9948

    Workaround for #9948. Warn devs to delete component CSS file along with theme generated file in one run to avoid webpack compilation errors and application restart. (cherry picked from commit e33ec10)

  • ⧉ Flow-client build fixed for Windows (#10815). PR:10819

  • ⧉ Extend and clarify valid tag names in LitTemplate or other elements (#10801). PR:10803. Ticket:9669

  • ⧉ Don't publish flow-client TS sources separately in JAR (#10765). PR:10795

    Improve performance of webpack build by only shipping precompiled JS of the flow-frontend TS sources, so webpack doesn't try to use the TS source files which is slower than using JS directly. The TS sources are still included in the sourcemaps (.js.map). This is a cherry-pick of 0476cd4 (from master to 6.0).

  • ⧉ Avoid ConcurrentModificationException in Binder (#10793). PR:10796. Ticket:9217

  • ⧉ Don't update bean property which is read-only bound (#10768). PR:10781. Ticket:9446

• ⧉ All changes