The micro-frontend approach is just a way to architecture big apps/teams. As long as you are serving the same assets, the browser outcome will be the same.
If you opt for a lazy loading approach: you will have to do a small request for the micro-frontend "runtime" (which decides which bundle to load and use) and an additional one for the actual app (the one the runtime decided to load).
If you opt for an eager loading approach: you will have both apps (with React and Vue) as part of your bundle and you will do only one request
You can come up with whatever loading approach you want to mitigate loading times & bundle size. Think of it as glorified code splitting if you want.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Curious about the bundle size and performance. Also, some lighthouse score maybe 🙂
The micro-frontend approach is just a way to architecture big apps/teams. As long as you are serving the same assets, the browser outcome will be the same.
If you opt for a lazy loading approach: you will have to do a small request for the micro-frontend "runtime" (which decides which bundle to load and use) and an additional one for the actual app (the one the runtime decided to load).
If you opt for an eager loading approach: you will have both apps (with React and Vue) as part of your bundle and you will do only one request
You can come up with whatever loading approach you want to mitigate loading times & bundle size. Think of it as glorified code splitting if you want.