[{"data":1,"prerenderedAt":77},["ShallowReactive",2],{"term-m\u002Fmonorepo":3,"related-m\u002Fmonorepo":60},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":54,"sitemap":55,"stem":58,"subcategory":6,"__hash__":59},"terms\u002Fterms\u002Fm\u002Fmonorepo.md","Monorepo",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"A monorepo is when you put all your different projects — frontend, backend, shared libraries — in one giant single repository instead of separate repos. It makes sharing code between projects easy, but the repo gets big and tooling gets complex.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"A monorepo is a single repository containing multiple distinct projects with well-defined relationships. Tools like Turborepo, Nx, and Yarn Workspaces optimise monorepo workflows with smart caching and dependency graphing. Used by Google, Meta, and many large-scale engineering orgs.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"We moved to a monorepo so the frontend and backend can share types.\" \u002F \"Monorepo CI pipelines only rebuild affected packages.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"general","A monorepo is when you put all your different projects — frontend, backend, shared libraries — in one giant single repository instead of separate repos.","intermediate","md","m",{},true,"\u002Fterms\u002Fm\u002Fmonorepo",[49,50,51,52,53],"Workspace","Codebase","Package","Dependency","Scaffold",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Fm\u002Fmonorepo","HwgDvCQLhx6rRA9tWzGfs5TgWPcStFMKEgAYFBv7h3M",[61,65,68,71,74],{"title":50,"path":62,"acronym":6,"category":40,"difficulty":63,"description":64},"\u002Fterms\u002Fc\u002Fcodebase","beginner","The codebase is the whole collection of source code that makes up a project — every file, folder, and line of code.",{"title":52,"path":66,"acronym":6,"category":40,"difficulty":63,"description":67},"\u002Fterms\u002Fd\u002Fdependency","A dependency is a package your project relies on to work. Your app depends on React to render UI, axios to make requests, and dotenv to read config.",{"title":51,"path":69,"acronym":6,"category":40,"difficulty":63,"description":70},"\u002Fterms\u002Fp\u002Fpackage","A package is a bundle of code someone else wrote and published so you don't have to reinvent the wheel. Need to parse dates? There's a package for that.",{"title":53,"path":72,"acronym":6,"category":40,"difficulty":63,"description":73},"\u002Fterms\u002Fs\u002Fscaffold","Scaffolding is when a tool auto-generates the skeleton of your project for you.",{"title":49,"path":75,"acronym":6,"category":40,"difficulty":42,"description":76},"\u002Fterms\u002Fw\u002Fworkspace","A workspace is how package managers understand a monorepo — they see multiple packages inside one repo and manage them together.",1776518296207]