4 ms·
I think you mean you can't have same element redeclared? Then yes this is still the case, and at least for now it will be - for any library that can output cust
by ergo14 7y ago
I think you mean you can't have same element redeclared? Then yes this is still the case, and at least for now it will be - for any library that can output custom elements. Every component is a real interactable HTML element, imagine <div> or <p> would work differently. I believe there is some work for multiple component registries but I'm not tracking the progress on that. This is HTML thing - it is not a library specific problem. It might get solved eventually https://github.com/w3c/webcomponents/issues/716 https://github.com/w3c/webcomponents/issues/716.
I come from python world where you have same restriction for all packages so it never occured to me as a serious problem :) We just pin ranges in libraries. And application itself pins specific versions in place.
- Vinnl 7y agoYes. I come from React, and if two components I depend on each depend on different versions of the same component, I can load them both no problem. When I worked with Web Components, that required that I contacted the authors of both components to get them to upgrade to the new version of the same time - which of course became exponentially more effort as we used more components.
- ergo14 7y agoThis is how HTML tags work currently. You are better off with something else if you want to sidestep this. At least for now.