Core Contributor Sprint Retro - July 8th - July 22nd

[ghassan (Ghassan Maslamani)]

@antoviaque

I’d like to understand why the various frontend packages seem to have a lot of conflicting dependency specifications and if there’s a reason why so many core packages don’t even support React 17. Context: fix: support running this frontend in “developer mode” on Tutor · openedx/frontend-app-library-authoring@76c1756 · GitHub

@kmccormick During the contributors meetup, @arbrandes indicated that this is caused by the current design, and that there are discussions on unifying dependencies, but there isn’t a clear answer yet. @ghassan has suggested and volunteered to do a discovery on this, and has a proof of concept that he will publish.

First I want to cleaify that are two issues that are related but are different.

• Peer depedecny issue: there are peer depednecy in some MFEs hence PR mentioned and this in accont MFE. This might or might be realted to have a consistent dependcies in MFEs. i.e. we might a consistant wrong version of library in all MFEs.
• Secondly having a consitant versions for shared libraires is an issue which I initailly started to research how to resolve because I wanted to create a monorepo version of common MFEs Why I wanted to create a monorepo, you can see the repo link below also relevant disccusion here.

Expirement repo is GitHub - ghassanmas/mfes-mono , I have added as much information as possible in Readme.md