My compliments on this component - I really like it.
FYI, I tried v1.1.1 with vaadin 14.2.0 and the post animation handler did not fire so I switched back to 1.1.0 and the handler works but in production I have this message
compani-1.1.0.jar!/META-INF/VAADIN/config/flow-build-info.json’ first match of ‘2’ possible
…and the whole app stops working.
Thanks for this info. I will check it…
Look like this issue, that came with the release of 14.2.0: https://github.com/vaadin/flow/issues/7858
The possible cause for this problem are duplicated versions of
You can check your project for duplicated component versions with
npx find-duplicate-dependencies
I hope the vaadin team will fix this pretty soon. Meanwhile I will try to find a workaround.
More Info, but less clarity. Something has gone very wrong (although I don’t know if it’s with your component or my project). I’m now trying a clean build with V14.1.25 and compani 1.1.0 and I’m getting the attached in the browser.
I have just tested compani 1.1.0 with Vaadin LTS 14.1.25 and it worked. Sometimes (when switching between Vaadin versions) you get problems with all those NPM packages (these problems should disappear with 14.2). When I change the Vaadin version, I do always manually delete
These files will be generated by the Vaadin maven plugin. This should clean all those depencencies.
Just FYI… a new maven archetype generated project 14.1.25 with 1.1.0 worked for me too.
But a fully clean build (removing all those files and folders as suggested and cleaning out the browser application) is still giving me the problem as shown in the image above. I’m taking deep breaths.
PS: The archetype maven build using v14.2 also has issues, without compani. https://github.com/vaadin/flow/issues/7858
well… there are some issues currently. Good luck!
Last update. The difference is whether I use -Pproduction or not.
If I use -Pproduction the request contains a ‘-es6’ suffix which fails. If I do not the suffix is not there and the request succeeds… the struggle continues.
Last update plus 1.
In order to make this work I had to
a. not use -Pproduction as descibed above
(Check out [this]
(https://vaadin.com/docs/v13/flow/advanced/tutorial-flow-runtime-configuration.html) link)
b. remove META-INF/VAADIN/config/flow-build-info.json from compani-1.1.0.jar.
The flow-build-info.json file is picked up by the framework and added to a list, the framework can only use one flow-build-info.json. If it randomly picks the one in compani-1.1.0.jar the application will not work at all. This can occur when the application is ‘[running from a jar]
(https://github.com/vaadin/flow/blob/075fb0282e949b159411ef3aa3d33a354826132b/flow-server/src/main/java/com/vaadin/flow/server/DeploymentConfigurationFactory.java#L372)’