Matthias Hryniszak
Matthias Hryniszak
Oh, and before anyone asks, the [@padcom/vite-federation-plugin](https://github.com/padcom/vite-plugin-federation) does nothing else than read values from `package.json` or if they are not present then to supply some defaults. Then the `@originjs/vite-federation-plugin` is...
When you change something in the component in the library vite (in dev mode, of course) will automatically patch the implementation in-memory and re-instantiate all the instances of components downwards....
If just the build -w worked...
Any news? It'd be really awesome to have it configurable and to actually see the problem when it is really there..
Any progress on that one?
Cute, https://github.com/iNavFlight/inav/issues/8691 says "Duplicate of https://github.com/iNavFlight/inav-configurator/issues/1616" and this one links back to https://github.com/iNavFlight/inav/issues/8691... or am I missing something?
I'm facing the same issue and also with components that are rendered based on content from a CMS. I am using GrapesJS as the page editor and having custom elements...
There's also the issue of custom elements with `shadowRoot` inside forms - described [here](https://www.hjorthhansen.dev/shadow-dom-and-forms/)
@LukeBridges You _might_ give the [@padcom/vue3-ce-noshadow](https://www.npmjs.com/package/@padcom/vue3-ce-noshadow) package a try. It is a hacked version of the `defineCustomElement` that allows you to create webcomponents that don't have the shadow DOM. The...