What’s the best way to structure a monorepo with multiple services (backend, frontend, shared‑utils) to avoid dependency confusion? #180611
Replies: 1 comment
-
|
Thanks for posting in the GitHub Community, @Suhebdevtechnosys! We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Discussions category is solely related to conversations around the GitHub product Discussions. This question should be in the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Discussion Type
Product Feedback
Discussion Content
If I keep all my services (backend, frontend, shared code) in one Git repository, how should I organize it so it’s clear which code depends on which libraries, and avoid conflicts between versions?
Beta Was this translation helpful? Give feedback.
All reactions