vaadin/flow 24.4.0.alpha2

Vaadin Flow 24.4.0.alpha2

on GitHub

Changes since 24.4.0.alpha1

All changes

New features

• Pass theme definition to bootstrap modifiers
  Commit · Pull request

  This is needed to be able to import the correct version of components in an addon, e.g. if the application uses Material you will break the app if you import the Lumo version of vaadin-button

• Allow disable component tracker
  Commit · Pull request · Issue

  Adds a configuration parameter that allows developers to disable component tracking.

Fixes

• Limit the requested items to a given threshold
  Commit · Pull request · Issue

  Limits the number of requested items from backend to a given threshold of ten pages. Exactly the same as #12003, but applied to HierarchicalDataCommunicator.

• Report errors when running commands to launch the IDE to open a file
  Commit · Pull request

• Permit access to custom PWA icons and favicon
  Commit · Pull request · Issue

  This change configures VaadinWebSecurity with an additional request matcher that grants access to everyone to custom PWA icons and favicon paths.

• Ignore final EOL when comparing types.d.ts contents
  Commit · Pull request

• Update stats.json for Frontend resources
  Commit · Pull request · Issue

  Includes resources under frontend folder in frontendHashes in dev bundle's stats.json to make them properly detected for changes when building bundles.

• Ignore plugins registration when dev-tools are disabled
  Commit · Pull request · Issue

  Prevents JavaScript errors caused by dev-tools plug-ins attempting to register themselves when the development tools are disabled.

• Handle inner classes in component tracker
  Commit · Pull request · Issue

  ComponentTracker location fails to determine the source file for inner classes. This change tries to identify the enclosing class before matching with location filename.

• Fix css module definition in typescript declaration file
  Commit · Pull request · Issue

  When importing styles in typescript sources, the import should contain the inline parameter (e.g. import styles from './some.css?inline'). The current module definition in types.d.ts does not handle the parameter, so TypeScript errors happen during build. This change updates the definition in Flow default types.d.ts file and handles upgrade of existing files.

• Update stats.json for WebComponentExporter resources
  Commit · Pull request · Issue

  Includes WebComponentExporter's generated web components under frontend/generated/flow/web-components in frontendHashes in stats.json, to make them properly detected for changes when building bundles.