Hi, i have vaadin 14.8.x tested with different versions. every time i have

Directory Date Range Picker
1

hi,

i have vaadin 14.8.x tested with different versions. every time i have a problem with the babelloader.

WARNING in ../node_modules/@vaadin/component-base/src/element-mixin.js?babel-target=es6 15:0-29
"export 'setCancelSyntheticClickEvents' was not found in '@polymer/polymer/lib/utils/settings.js'
 @ ../node_modules/@vaadin-component-factory/vcf-date-range-picker/src/vcf-date-range-picker.js?babel-target=es6
 @ ../node_modules/@vaadin-component-factory/vcf-date-range-picker/theme/lumo/vcf-date-range-picker.js?babel-target=es6
 @ ../node_modules/@vaadin-component-factory/vcf-date-range-picker/vcf-date-range-picker.js?babel-target=es6
 @ ../target/frontend/generated-flow-imports.js?babel-target=es6

WARNING in ../node_modules/@vaadin/component-base/src/element-mixin.js?babel-target=es5 26:0-29
"export 'setCancelSyntheticClickEvents' was not found in '@polymer/polymer/lib/utils/settings.js'
 @ ../node_modules/@vaadin-component-factory/vcf-date-range-picker/src/vcf-date-range-picker.js?babel-target=es5
 @ ../node_modules/@vaadin-component-factory/vcf-date-range-picker/vcf-date-range-picker.js?babel-target=es5
 @ ../target/frontend/generated-flow-imports.js?babel-target=es5

then the webcomponents are not running in deployment and i have a blank page.

2

Found out the problem.
Your NPM-Version annotation has a bug :)

@NpmPackage(
    value = "@vaadin-component-factory/vcf-date-range-picker",
    version = "^4.8.10"
)

This leads in Vaadin-14 WebPack to loading the 4.9.0 (auto update for newer minorversion).
But 4.9.0 using vaadin-23 and both are not compatible.

3

Hi, this issue was fixed in version 1.10.0.

Regards.