Closed thewilkybarkid closed 4 years ago
Had a good chat with @davidcmoulton, sounds like we're ok with having separate bundles for each service as the amount of shared styles is pretty small. And the conflicts between pages and components is a process problem rather than technical.
However, fonts (and possibly some other assets) should be shared somehow.
Does this mean the /head
of a microfrontend could return a data structure rather than HTML to help with de-duplicating the <link>
tags or whatever is used to bring in the assets?
A scenario that could put constraints with this is how to deal with different versions of this shared assets. Assume you wouldn't want two different fonts in use at the same time does it imply they need an atomic change across frontends that depend on them?
Moving transclusion thoughts to https://github.com/libero/publisher-micro-frontend-experiment/issues/6.
Good to close assuming #6 is fine? (So asset bundles per page frontend, and transclude assets from component frontends using ESIs.)
Hasn't addressed the sharing of e.g. fonts, but I'm happy with somehow.
Just discussed with @davidcmoulton, and a Google Fonts approach might work. Details to be ironed out later, but since we're not styling for a while think it's ok.