@yassinebouchoucha

I transformed my enterprise ERP solution from monolith create-react-app to micro-front-ends architecture with webpack 5 Module Federation: that was very risky move: we went through 3 weeks of red and blank screen of errors, rethinking some feature implementation, debugging MaterialUi Css,  and re-working deployment pipeline to production, and added complexity to incoming junior developer... in total 3 month without updating our customer product.
After that the effort and sacrifice worth it, the rate at which we implement new big feature or ERP module is scaled to 5x time faster, and we can work independently  on single business domain.
Thank You Jack, your channel helped me to take this strategic decision !

@alekseikolesnikov6320

One of the best videos which explains Module Federation concept. Now I finally know where I did my mistakes in a solution. Thanks!

@dannybrown2698

This is excellent. Item number four here, and your separate video on semantically versioned module federation, were incredibly helpful.
I understand why you don't spend more time on detailing all of the different defensive strategies, but it is a good call out that the contract is something to be aware of.

@cherryfuchs

That error boundary tip was new to me. Thank you very much

@leonidas7692

Excellent work through of these issues. As someone behind the curve, I barely followed along on the code, but I understood from the explanations of the conditions for each scenario. Really impressive grip on your tools and frameworks in addition to being lucid on the solution architecture!

@dars1816

This is high-quality. Thank you

@garyb2160

Jack, Thanks for making this video.

@jacobsheets671

I love that you talked a bit about what this architecture looks like in a real deployed environment (ie. assets vs. server).  Sometimes tutorials focus so much on the dev setup you forget a production-ready solution needs more than that.  I'm also really curious about the sharing of types and if there is a way to share those types across repositories and projects.  You could publish an NPM package with the types, and I'm sure you wouldn't be changing the type definitions as often as the components themselves.  Would that be the only way?

@notramiras

Nx's module federation boilerplates have cross-module typescript coverage.

@garywaddell6309

Wow Jack you fly through these videos, you definitely know your sh!t. Great content!

@matthew1106

Thanks Jack! For Q4 I'm rolling out MF for my team.

@marcelsdev

Thanks for the explanation and examples :)

@cheikhsaadbouh5847

thank you for this valuable information , well explained

@EthanStandel

I know that this is an older video (by YT standards), but I just have to say... if you're going to make the remote package and the host app both rely on a @types library then what's the point of module federation? Why wouldn't you just publish the remote app as a package and then make sure that the host updates... that way you can catch any errors created by a new version at build time rather than run time?

@bintang9080

Good solution thanks

@chenrvn

Thanks, Jack Gr8 Video!! :)

@Pixiethebirb

Thank you for sharing your knowledge on module federation and SSPA. All your videos display webpack based solutions. We are trying to host a react app on a JSP based legacy home applications . Is this an idea worth pursuing? please help understand the challenges from your experience.

@androidgeeking

Do you have  a video covering routing with MFEs? Trying to figure out how you would export your routes or guarded routes from remote.

@MrCherry3475

Thanks for great video, it helps a lot! I thought we could achieve microfrontend without shared repo, but as we use TypeScript - we need to have shared types, version them and deploy to each microapp?

@AurelioPita

I've seen a lot of your videos. In my understanding, all these tools were created so we can implement counters in many different ways.