vaadin/flow 23.0.1

Vaadin Flow 23.0.1

on GitHub

Changes since 23.0.0

All changes

Fixes

• Distinct dom-module ids (#13246)
  Commit · Pull request · Issue

  generated for distinct @CssImports

• Allow all Java features when parsing endpoint code (#13134) (CP: 23.0)
  Commit · Pull request

• Do not load service worker with Vite in dev mode in 23.0
  Commit · Pull request · Issue

  Vite does not serve a service worker in dev mode in 23.0. It has already been fixed for 23.1 in #12857 and #12928

• Use configured error path instead of hard coded one (#13217)
  Commit · Pull request

• Check postinstall before run (#13167)
  Commit · Pull request · Issue

  Check that there is a postinstall script available before executing it to not receive error in the logs.

• Always lock chokidar version to avoid chokidar 2 (#13223)
  Commit · Pull request · Issue

  chokidar 2 has known security issues that will show up when auditing. These issues are probably impossible to exploit as dev tools do not get input from a user but we should still fix them. This is 1:1 with the pnpm locking in pnpmfile.js

• Do not accidentally invoke a global node through postinstall scripts (#13214)
  Commit · Pull request

  If a postinstall script contains e.g. "node install.js" like esbuild then it will use "node" from PATH to run the script. In this case, the Vaadin installed node must come first, before any other node versions mentioned in the PATH

• Include vaadin-spring in flow-bom (#13210)
  Commit · Pull request

  This is needed so that when overriding the Flow version in a project you will get the correct vaadin-spring version also

• Never save /error as the navigation target after login (#13212)
  Commit · Pull request · Issue

• Do not assume a tool is broken if it outputs to stderr (#13220)
  Commit · Pull request · Issue

  In some cases, npm -v can prefix the version by something like this printed to stderr (node: 1124) [LRU_CACHE_OPTION_maxAge] DeprecationWarning: The maxAge option is deprecated. please use options.ttl instead This should not be interpreted like npm does not work.

• Do not remove overrides for manually added dev dep references (#13189)
  Commit · Pull request

  If a devDependency reference has been manually added to override do not clean those.

• Alter handling of cases where key value is not present (#13174)
  Commit · Pull request · Issues 13004, 13173

• Let vaadinPush.js script always be served by Vaadin (#13158)
  Commit · Pull request · Issue

  vaadinPush script url doesn't took into account potential servlet path and was always relative to context path; this can cause the script not to be served by Vaadin StaticFileHandler, but directly by container or non Vaadin handlers (for example in Spring applications). This change makes the script URL relative to servlet path, so it is forced to be served by Vaadin StaticFileHandler.

• Configure Spring Security to handle vaadin.urlMapping (#13143) (CP: 23.0)
  Commit · Pull request

  When setting vaadin.urlMapping to a value different from default (/*), spring security redirects after login was to the wrong url. This change updates spring security configuration (e.g. request matchers and success handler) to take care about urlMapping.