github vaadin/flow 23.0.3
Vaadin Flow 23.0.3

latest releases: 23.5.12, 24.6.5, 24.5.13...
2 years ago

Changes since 23.0.2

All changes

New features

  • Allow navigation with RouterLinks when inert (#13331)
    Commit · Pull request · Issue

    Server-side modality feature attempted to block navigation when a modal component is active. This blocks some legitimate use cases when one wants to use RouterLinks inside a modal component. With the current router implementation, it is not practically possible to separate between RouterLinks that are inside a modal from those that are outside (inert). Moreover, navigation cannot be fully controlled on the server side anyway. Therefore, the development team decided to reverse the decision to block RouterLinks when the UI is inert. This PR allows navigation via RouterLinks even when the UI is inert.

Fixes

  • Only import the needed parts of lumo-styles (#13320)
    Commit · Pull request · Issue

  • Enable use of tsx files in add-ons (#13323)
    Commit · Pull request · Issue

    Also copy any tsx file resources form add-on folders.

  • Use Node 16.14.2
    Commit · Pull request

    Node 16.14.2 contains some security related fixes

  • Warn for duplicate npm classes (#13291)
    Commit · Pull request · Issue

    If encountering multiple NpmPackage annotations with different versions log a warning and inform of choice taken.

  • Do not run any Maven goals automatically in Eclipse / VS Code (#13302)
    Commit · Pull request

    It seems like especially VS Code can start running prepare-frontend over and over again in some cases which will interfere with an externally running mvn spring-boot:run process that will continuously restart because of an updated target/classes/META-INF/VAADIN/config/flow-build-info.json There should be no need nowadays to run prepare-frontend from Eclipse at all as it is run through the dev server if needed.

  • Avoid manipulate absolute stream resource URL in web-component mode (#13296)
    Commit · Pull request · Issue

    In web-component mode resource URLs are always prefixed by serviceUrl, but sometimes the URL is already absolute (e.g. in Liferay). With this change absolute URLs are used as-is also in web-component mode.

  • Don't use plugins through npm (#13254)
    Commit · Pull request · Issue

    Decouple theme/webpack plugins from npm.

Don't miss a new flow release

NewReleases is sending notifications on new releases.