github vaadin/flow 24.0.0.alpha3
Vaadin Flow 24.0.0.alpha3

latest releases: 23.5.5, 24.5.0.alpha20, 24.5.0.beta1...
pre-release23 months ago

Changes since 23.3.0.alpha2

All changes

New features

  • Allow specifying vaadin.devServerPort to connect to an already running dev server
    Commit · Pull request

    This is only meant for debugging the dev server itself and the connection to it

  • Allow excluding URLs from being handled by a root mapped Vaadin Spring servlet
    Commit · Pull request · Issue

    This makes it possible to make services like swagger work correctly even when Vaadin is mapped to the context root.

Fixes

  • Use access and not lock
    Commit · Pull request · Issue

    Use access so that we do not deadlock.

  • AbstractDataProvider serialization
    Commit · Pull request · Issue

    Replace lambda with anonymous inner class in AbstractDataProvider to fix serialization issue(s). Test available in flow-components project since the issue only happens when the data provider is used with a grid.

  • Synchronize pwa handler on map
    Commit · Pull request

    Synchronize pwa handler on the requestHandlerMap instead of locking the session. Locking and unlocking session may fire a push event that might make the server client sync faulty. touches #14797

  • Old node installation
    Commit · Pull request · Issue

    node installation we check the correc path for npm script.

  • Locking on FeatureFlags instead of VaadinContext (#13962)
    Commit · Pull request · Issue

    Only lock on FeatureFlags when checking for wrapper and initializing

  • Defer location and query tracking
    Commit · Pull request · Issue

    Track of location and query string after response from server happens too early when handling server side navigation, because history.pushState is executed within a setTimeout. This change defers the tracking to the next event loop cycle in order to get the correct values.

  • Redirect if refresh token is in push response also
    Commit · Pull request · Issue

  • Ignore nonexistent nodes during resync
    Commit · Pull request · Issues 14232, 14470

    Ignore changes for nodes that are not available in the tree when a resync is underway. This will get the page to a working condition after a resync as all changes for existing nodes are executed.

  • Attach polymer binding callback to a promise that always resolves
    Commit · Pull request · Issue

    Polymer binding callback was attached to the promise returned by customElements.whenDefined, but this promise may never complete if the input element is not a custom element, causing memory leaks on browser because of element capture. This change introduces a new promise that completes either when whenDefined is fulfilled or after a fixed timeout, allowing the garbage collector to clean resources.

  • Write version.json from the currently constructed package.json
    Commit · Pull request

    The earlier logic was like 1. Read package.json 2. Modify package.json in memory 3. Generate version.json based on package.json file 4. Write modified package.json to file Where step 3 ignored what was done in step 2

  • Throw exception if Vite and deprecatedV14Bootstrapping are used
    Commit · Pull request

    Interrupts application's bootstrapping if Vite + v14 Bootstrapping are detected with the message to fallback to Webpack, sine Vite is not supported yet with this mode.

  • Cancel previous flush request if new one is forced
    Commit · Pull request · Issue

  • Do not assume a /VAADIN/ mapping is the real servlet mapping*
    Commit · Pull request

  • Do not use a fixed download root
    Commit · Pull request · Issue

    As the default download root might be different depending on the used system we should not use a hardcoded default if user has not given a download root.

  • Make system property feature flag value always override stored one
    Commit · Pull request · Issue

    Enable or disable a feature flag by providing a system property is not working when feature flags file is loaded by a ResourceProvider. This change makes system properties always take precedence over stored values

  • Make paths work as version numbers in @NpmPackage
    Commit · Pull request · Issue

  • Only map websockets to servlet path and not any sub paths
    Commit · Pull request

  • Use es2020 for Vite, es2019 for webpack
    Commit · Pull request · Issue

Don't miss a new flow release

NewReleases is sending notifications on new releases.