vaadin/flow 24.0.0.beta3

Vaadin Flow 24.0.0.beta3

on GitHub

Changes since 24.0.0.beta2

All changes

Breaking changes

• Use feature detection to show the unsupported browser page (#15813)
  Commit · Pull request · Issue

  This removes the WebBrowser.isTooOldToFunctionProperly() method as it is no longer possible to determine this information based on the user agent.

Fixes

• Ignore missing files in theme processing (#15896)
  Commit · Pull request · Issue

  During theme processing, a file detected as existing may be delete before it gets copied, causing a ENOENT (No such file or directory) error. After such failure, dev server live reload stops working. This change catches errors in file copy operations, ignoring ENOENT and propagating other failures.

• Ignore old Vaadin provided dependencies for bundle resolution (#15939)
  Commit · Pull request

  Ignores the dependencies provided by older Vaadin versions and not present anymore in a target Vaadin version. Examples: polymer iron-list or deprecated Vaadin web components with "vaadin-" prefix.

• Do not process *.css.js as CSS files (#15914)
  Commit · Pull request · Issue

  The include/exclude patterns for postcssLit are glob patterns and *.css\?* matches e.g. "foo.css.js`

• Add reserved /VAADIN segment to the theme pattern (#15917)
  Commit · Pull request · Issue

  Theme files should be served for a pattern /VAADIN/themes/ like for the hot deploy mode with Vite.

• Do not warn about eval that the user cannot affect (#15919)
  Commit · Pull request

• Only show development tools code tab when Flow is used (#15911)
  Commit · Pull request · Issue

• Package generation (#15916)
  Commit · Pull request · Issue

  package.json in-memory generation should take into account versions files