3 ms·
If reusable frontend code for your within a single organization or business unit is important, then having separate repos is crazy. A monorepo with separate bu
by eezing 3y ago
If reusable frontend code for your within a single organization or business unit is important, then having separate repos is crazy.
A monorepo with separate build pipelines is better, but still unnecessarily complex.
A framework like Next.js can do the heavy lifting for you. One build pipeline where components are shareable, and pages/routes ans entry are isolated during development and can be deployed independently if required.
- JCharante 3y agoHow is it crazy? I think a lot of big companies have design standards and then some teams create UI libs that follow those standards (and then the UI/UX designers will use the design standards while devs use the ui lib). That’s plenty of reusability, and if you really need to share some components between two MFEs then maybe they should just be 1 MFE. A page footer could easily just be a small react component library built on top of the ui lib, and then everybody can just import it and stick it at the bottom of their MFEs.