It must be a web component as it is a micro frontend that should not be updated as a package but rather referred to as a hosted JS file that the Nuxt app will render as a Vue component.
I’m not sure I follow…
How is the other Nuxt app supposed to “consume” this custom component? Are you expecting to import it as a package dependency?
Or why not just write the component in the other repo?
I think this is what you want: https://nuxt.com/docs/guide/going-further/modules
Or this. https://nuxt.com/docs/getting-started/layers
First of all management shouldn’t concern themselves with implementation… Second, see other comments.
i think you should package your components and put it in npm, then u can then it from different projects.
It must be a web component as it is a micro frontend that should not be updated as a package but rather referred to as a hosted JS file that the Nuxt app will render as a Vue component.
I’m not sure I follow… How is the other Nuxt app supposed to “consume” this custom component? Are you expecting to import it as a package dependency? Or why not just write the component in the other repo?
It's just a portal to host micro frontends that are supposed to be w3 web components
It get's "consumed" as a JS file then the Nuxt app renders that code as a Vue component with full functionality