So glad you made it fast and straighfoward, wish all the tutorial were this fast paced (without sleep-inducting writing)
I'm gonna be preaching this for a long time. This is quite possibly the coolest thing ever. I really am dying to work on a project like this.
Hi Jack, Thanks for putting out these videos. I wanted to get into the frontend architecture but wasn't able to find the correct path. I think you hold great knowledge. Thanks for sharing it with us.
The really good way to describe about Module Federation.
This is mega awesome, the missing piece of the puzzle for my current project :) Thanks for a very good explanation!
Super helpful!
thanks Jack, this is what i needed to get it, you making a good job, awesome
Great content and great explanation Jack!
Awesome well explain
Im going to subscribe. "This is the way"
Thanks for the content!
Although this is a very cool way to share code, I am still very skeptical on the governance at the organizational level. If each app is managed by two different teams, doesn't that mean that one team is now managing the dependency of the other? What if the Home app no longer wants to use ProductCarousel? Are they forced to keep the component within the Home codebase even though it's obsolete? Should the ProductCarousel be transferred to another team? Would that force any other teams using ProductCarousel to have to update their code? Why should be the Home app be the owner of this dependency and not the Search app? I have many questions.
This is amazing.. cant wait for webpack v5 o/
Hello Mr. Herrington My micro-projects are exposed on the server and the project they are remote is in my local, my problem is that fonts are not displayed in my local project Which part do you think has a problem?
Hi Jack! This is super cool!
nice 🔥
I'm curious how do we use micro-frontends with Module Federations across different repos? Say you have Home and Search on different repos. How would Home leverage code from Search compiled from a separate repo
Not sure how does this differs from the Bazel. I can already to make hermetic app-shells and reusable widgets and components, which i can throw in wherever i want. To use dynamic imports, reducer injection and other things. Sure, it's mono-repo centric so everything becomes shareable. On top of that i can build Protobuf type declarations and share them between FE and BE with ease. If any single shared piece gets updated, then chain of incremental builds is triggered testing every consumer of that updated lib/component/whatever. Single tool for the all build and deployment requirements for booth, the back-end and front-end. The only use-case i can see so far is related to local DX. Like.. simplified version of spinning up dev environment locally. But.. definitely really interested to dig deeper into this. Nice stuff.
I can't wait to get my hands dirty with this!!! Thanks
@zoecarlibur