Hey that's great! I appreciate someone picking up on the part at the end about future follow-ups. Definitely plan to make it happen.
I think right now one of the biggest challenges on the monorepo topic isn't even setting it up -- it's coming up with a good little scenario/example to show WHY you would want to use the monorepo, without being too complex, but also being a bit more real-world than just the "hello world" packages that the basic tutorials use.
Hey that's great! I appreciate someone picking up on the part at the end about future follow-ups. Definitely plan to make it happen.
I think right now one of the biggest challenges on the monorepo topic isn't even setting it up -- it's coming up with a good little scenario/example to show WHY you would want to use the monorepo, without being too complex, but also being a bit more real-world than just the "hello world" packages that the basic tutorials use.
I agree, In my current project I decided to do mono repo and I still ask my self until now why I need to do this approach.
In my case I have 5 website (next js) that share ui-lib and backend.
And I think maybe it easy to communicate with team and track dependencies version (ui-lib) if I apply monorepo.
But now Iām not sure about it lol š