Changing vaadin to vaadin-core dependency can break the application with 14.2
See original GitHub issueSteps to reproduce
- Use Beverage Buddy test application
- Check that it has Vaadin version 14.2
Change the project to use
<dependency>
<groupId>com.vaadin</groupId>
<!-- Replace artifactId with vaadin-core to use only free components -->
<artifactId>vaadin-core</artifactId>
...
</dependency>
When application starts it is broken and you can find exception on console log
Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': the name "vaadin-overlay" has already been used with this registry
at eval (webpack-internal:///../node_modules/@vaadin/vaadin-dialog/node_modules/@vaadin/vaadin-overlay/src/vaadin-overlay.js:1098:16)
at Module.../node_modules/@vaadin/vaadin-dialog/node_modules/@vaadin/vaadin-overlay/src/vaadin-overlay.js (http://localhost:8080/VAADIN/build/vaadin-bundle-36969be0b59ccab111c7.cache.js:1872:1)
at __webpack_require__ (http://localhost:8080/VAADIN/build/vaadin-bundle-36969be0b59ccab111c7.cache.js:20:30)
at eval (webpack-internal:///../node_modules/@vaadin/vaadin-dialog/src/vaadin-dialog.js:5:102)
at Module.../node_modules/@vaadin/vaadin-dialog/src/vaadin-dialog.js (http://localhost:8080/VAADIN/build/vaadin-bundle-36969be0b59ccab111c7.cache.js:1908:1)
at __webpack_require__ (http://localhost:8080/VAADIN/build/vaadin-bundle-36969be0b59ccab111c7.cache.js:20:30)
at eval (webpack-internal:///../node_modules/@vaadin/vaadin-dialog/theme/lumo/vaadin-dialog.js:3:79)
at Module.../node_modules/@vaadin/vaadin-dialog/theme/lumo/vaadin-dialog.js (http://localhost:8080/VAADIN/build/vaadin-bundle-36969be0b59ccab111c7.cache.js:1932:1)
at __webpack_require__ (http://localhost:8080/VAADIN/build/vaadin-bundle-36969be0b59ccab111c7.cache.js:20:30)
at eval (webpack-internal:///../target/frontend/generated-flow-imports.js:36:108)
Collaps
Removal of node_modules, package-lock.json, … and doing clean build does not help.
Apparently this is not happening with all applications.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Having vaadin.pnpm.enable = false breaks an application · Issue ...
The initial idea was to avoid duplicates with vaadin-shrinkwrap but it didn't work out as we expected. Transitive dependencies can still bypass the...
Read more >package.json dependency version mismatching on tutorial ...
all vaadin 14 projects I downloaded got some dependency version matching error on npm install, I tried remove package.json & node_modules, none of...
Read more >Build error on Bamboo server. - Vaadin
I am trying to build a Vaadin 14 application on a bamboo server running on Centos 7. I am getting the following error...
Read more >New Guava Dependency Vaadin-CDI breaks TomEE ...
Hello, I am using the vaadin-cdi 1.0-snapshot in a project, and today, the deployment under tomee 1.6.0.2 via tomee:run broke with symtoms simmilar...
Read more >Why Vaadin-maven-plugin run with multiple versions?
I have only one maven plugin in my project which is vaadin-maven-pluging: 14.1.25 . Can someone explain why does it happen? pom.xml <project...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mvysny as said above it was fixed after the tag update. So no need to wait for anything.
So, is it fixed now, or do we need to wait for Vaadin 14.2.1?