Turborepo (monorepo) might be the proper answer over module federation, if code sharing is the main concern but building the whole repository is a deal breaker.
I could see module federation as a way to split the frontend between teams that communicate with contracts, in a way similar to microservices.
If the frontend team is relatively small or highly communicative, just go with a monorepo! Plus we could share types/validations between the backend and frontend more easily than packagings. wink, wink
Great demo on the module federation! I had a attempt at it using nuxtjs before but ended up working with a monorepo too.
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.
Turborepo (monorepo) might be the proper answer over module federation, if code sharing is the main concern but building the whole repository is a deal breaker.
I could see module federation as a way to split the frontend between teams that communicate with contracts, in a way similar to microservices.
If the frontend team is relatively small or highly communicative, just go with a monorepo! Plus we could share types/validations between the backend and frontend more easily than packagings. wink, wink
Great demo on the module federation! I had a attempt at it using nuxtjs before but ended up working with a monorepo too.