2025-01-30 Frontend Working Group Meeting Notes: React Compiler, frontend-base updates
- Adolfo Brandes
Date, time, location
Date:Jan 30, 2025 at 15:00 UTC (timezone converter)
Location: https://meet.google.com/cxz-yjwi-gvi
Discussion topic(s)
React Compiler exploration, frontend-base updates.
🎥Recording
Video: Frontend Working Group Meeting - 2025/01/30 12:00 GMT-03:00 - Recording
Chat: Frontend Working Group Meeting - 2025/01/30 12:00 GMT-03:00 - Chat
Transcript: Frontend Working Group Meeting - 2025/01/30 12:00 GMT-03:00 - Transcript
Participants
Adolfo Brandes
Brian Smith
Tony Busa
Juan Carlos Iasenza
Max Frank
🤖 Summary
1. React Compiler Discovery & Implementation
Brian Smith shared progress on React Compiler exploration, documenting findings in a wiki page.
React Compiler (experimental, coming in React 19) automatically memoizes code, improving maintainability and performance.
Memoization optimizations primarily benefit non-memoized codebases; existing optimizations will see minimal performance gains.
Eslint Plugin identifies violations of React’s rules, helping improve code quality even before adoption.
Next Steps:
Enable React Compiler eslint rules as warnings to start fixing issues.
Address compilation errors caused by missing type handling (undefined values).
Use React Scan to analyze rendering and FPS drops.
2. Frontend Base & Module Federation Progress
Module Federation (MF) & Composability Work aims to standardize frontend architecture and dependencies.
First step: Convert existing MFs to depend on Frontend Base instead of older build platforms.
Naming Scheme: MF terminology will remain until a formal naming structure is decided.
Changes in Header/Footer Handling:
Header/Footer will be loaded by the shell instead of being instantiated in each MF.
Customization for different operators (e.g., MIT, Tutor) will be configurable via slots.
Users can override the default configuration while maintaining flexibility.
Configuration Overhaul:
New “Site Config” system will replace the current M Config JS structure.
Operators will define modules, slots, and plugins in Site Config instead of hardcoding in MF.
Frontend Plugin Framework will integrate into Site Config for easier plugin management.
Deployment Strategy:
MFs will not necessarily be NPM packages; they can be built and stored in S3 or other storage, loaded via Module Federation (remoteEntry.js approach).
3. Roadmap & Next Steps
Continue refining React Compiler linting rules and gradual adoption strategy.
Frontend Base adoption will be incremental (first focusing on dependencies, then transitioning to the full shell-based system).
Operators (e.g., Tutor, MIT) will have control over how modules and configurations are structured.
Future discussions on Server-Side Rendering (SSR), but not a priority yet.