One of the fundamental challenges associated with micro-frontend architecture lies in managing dependencies and ensuring efficient resource utilization. By their very nature, micro-frontend applications tend to be independent, often leading to the inclusion of their own set of dependencies. This can result in the same libraries, or even different versions of the same libraries, being bundled multiple times across the various micro-frontends within a single application. Consequently, the benefits of using a package manager at the overall application level are diminished. This duplication of dependencies leads to larger overall bundle sizes, requiring end-users to download more data when accessing the application. The increased download size directly impacts the rendering time of the application, which in turn can negatively affect Google Web Vitals scores and ultimately the website's SEO performance. The inherent independence sought in micro-frontends can thus paradoxically result ...