2024-06-06 Frontend Working Group Meeting Notes: More module federation (OEP-0065)

 Date, time, location

• Date:Jun 6, 2024 at 15:00 UTC (timezone converter)

• Location: https://meet.google.com/cxz-yjwi-gvi

 Discussion topic(s)

Module federation (OEP-0065)

🎥Recording

• Video: https://drive.google.com/open?id=1i-xIgB5IpYb_fHyrAsHQLab3_2GVq3Rq&usp=drive_copy

• Chat: https://drive.google.com/open?id=1pumQQzEtql5NiU4atNZsgeoXiUQUe-7u&usp=drive_copy

• Transcript: https://drive.google.com/open?id=1Iy5WwjYvSS3C6sMl2bysV9UT3yTHuDLuVtzMa9XTYTE&usp=drive_copy

 Participants

• Adolfo Brandes

• Brayan Cerón

• Brian Smith

• Fox Piacenti

• Hina Khadim

• Jason Wesson

🤖 Summary

1. David's Solution for Frontend Build Testing:

   • David discovered a method to ease the long-standing issue of testing MFEs with frontend builds.

   • Solution involves using local copies of frontend builds set as files and modifying Webpack loaders.

2. Module Federation Implementation:

   • Discussion on the architecture and placement of OEP-0065 changes within the codebase.

   • Transition from single-page applications (SPAs) to module-based architecture using module federation.

   • Multiple options considered for transitioning, including incremental changes within the frontend app repo and separate build targets.

3. Challenges with Current Approach:

   • Issues with requiring multiple PRs for changes across repos (modules and apps).

   • Exploring alternatives like mini monorepos or maintaining separate directories within a repo to ease development and deployment.

4. Future Direction for Frontend Development:

   • Supporting both SPAs and module-based development simultaneously.

   • Potential solutions for maintaining consistency and ease of development while transitioning.

5. Customizability and Compatibility Concerns:

   • Maintaining the ability to run MFEs independently.

   • Ensuring new changes are backward compatible.

   • Discussion on integrating front-end plugin framework (FPF) into new module federation architecture.

6. Addressing Specific Issues and Development Needs:

   • Considerations for enterprise versus open-source implementations.

   • Handling forks and customizations within the module federation setup.

   • Integrating dependencies like front-end build and front-end platform in a modular approach.

7. Next Steps and Action Items:

   • Awaiting David's ADRs (Architecture Decision Records) for further clarity.

   • Potential for a modularity summit to discuss and iron out implementation details.

   • Ensuring backward compatibility and ease of transition for developers.

Conclusion:
The meeting concluded with a consensus to explore incremental changes while maintaining backward compatibility and preparing for a larger modularity summit. The team will review David's ADRs and continue discussions on improving the frontend development process.

 Action items

 Decisions