Vaadin Flow 24.2.0.alpha3

Changes since 24.2.0.alpha2

All changes

New features

• Dispatch popstate event on server-side navigation
  Commit · Pull request

Fixes

• Do not force chokidar version
  Commit · Pull request

  The old chokidar version was used by webpack 4

• Add missing hint for native build
  Commit · Pull request

• Prevent PWA registry lookup when VaadinServlet is not initialized
  Commit · Pull request · Issue

  When Java hot reload is enabled, it is possible that VaadinServlet will receive requests even if its destroy method has been invoked. When this happens, getting the PWA registry may fail with an NPE because of VaadinServlet optimizations for servlet initialization. This change prevents getting the PWA registry if the VaadinServlet is not initialized or has been destroyed

• Set restart monitor before checking for dev server connection
  Commit · Pull request

  If hot reload is enabled, e.g. with Spring Dev Tools, during Java server restart the check for active dev-server connection may temporarily fail because the dev-server is restarting. This change finds and sets the currently active restart monitor before checking for dev-server connection, so that the check will wait for a potential restart to complete.

• Prevent writing service worker on filesystem in dev mode
  Commit · Pull request

  When running in dev mode, the service worker should be served from memory and not written to the filesystem, to avoid potential endless restarts when Spring dev tools are in use. This change fixes a regression introduced when service worker compression was implemented, that causes sw.js to be written to the filesystem also in dev mode.

• Report exception if filewatcher fails to start
  Commit · Pull request

  Related to #17159

• Use dark color scheme for dev tools
  Commit · Pull request