If we need to share types or utilities between the frontend and the backend and we don’t want to duplicate them on both projects, we have to create a third repository and consume them as an external package for both projects.Įach time we modify the shared package, we have to build and publish a new version. Let’s say we’re building a full-stack application both the frontend and the backend are two separate projects, each of them placed in a different repository - this is a polyrepo. Here’s a representation of the structure of a monorepo and a polyrepo (source can be found here): It has a small learning curve and a low barrier to entry - whether you’re just starting out with monorepos or are experienced and looking to try different tools in the ecosystem. It’s fast, easy to configure and use, independent from the application technologies, and can be adopted incrementally. Turborepo is one of the best monorepo tools in the JavaScript/TypeScript ecosystem. Monorepos facilitate project management, code sharing, cross-repo changes with instant type-checking validation, and more.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |