-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught NotSupportedError: Failed to execute 'define' on 'CustomElementRegistry': the name "vaadin-lumo-styles" has already been used with this registry #7956
Comments
@Artur- is there any workaround available for this |
If some old library depends on |
Hi @web-padawan The problem is the old library(with older vaadin version ) has dependency @vaadin/[email protected] and when im trying to installing the @vaadin/date-picker:24.4.8 it has dependency of @vaadin/[email protected] , so bcz of that im getting this error 'CustomElementRegistry': the name "vaadin-lumo-styles" has already been used with this registry. |
Starting with Vaadin 20 we changed all components to use unified version. Mixing different versions of Vaadin components is not supported. This is why you need to make sure your dependencies depend on While it's possible to add |
Description
In my angular app im trying to use vaadin date picker component for that in my package json
{
@vaadin/date-picker:24.4.8
some-other-library:x.x.x
}
so here my some other library aslo has some vaadin dependencies and vaadin date picker also have the lumo style dependecies so bcz of the two different version of lumo styles my app is breaking with the below error.
Uncaught NotSupportedError: Failed to execute 'define' on 'CustomElementRegistry': the name "vaadin-lumo-styles" has already been used with this registry
Expected outcome
how to resolve them
Minimal reproducible example
Steps to reproduce
if we some other old vaadin components library vaadin-date-picker:4.3.0 and if im using newer version also then imgetting the above error
Environment
Vaadin version(s): v24
OS: window s
Browsers
No response
The text was updated successfully, but these errors were encountered: