Dependency Management in Monorepos
Explore techniques for managing internal and external dependencies across multiple projects within a monorepo.
Dependency Management in Monorepos is a free Git Advanced: Monorepo, Submodules & Workflows lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Git Advanced: Monorepo, Submodules & Workflows learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Monorepo Dependencies Explained
Welcome to dependency management in monorepos! In a monorepo, many projects live together in one Git repository.
This setup brings unique challenges and benefits for how these projects share and rely on code.
- Internal Dependencies: When one project in the monorepo uses code from another project in the same monorepo.
- External Dependencies: When projects use third-party libraries or frameworks (like React or Lodash).
Internal Dependencies: Code Sharing
One of the biggest advantages of a monorepo is easy code sharing. Imagine you have a shared UI component library and several applications using it.
Instead of publishing and consuming it as a separate package, you can reference it directly within the monorepo.
This simplifies development, testing, and ensures consistency across your applications.
External Dependencies: Third-Party Libraries
Just like any project, those in a monorepo often rely on external, open-source libraries. Think of popular tools like Node.js packages (e.g., Express, Axios) or Java libraries (e.g., Spring Boot, Guava).
Managing these can be tricky. Different projects might need different versions of the same external library, or you might want to enforce a single version across all projects for consistency.
Package Managers & Workspaces
For languages like JavaScript, package managers such as npm, Yarn, or pnpm are essential. They typically introduce a concept called workspaces.
Workspaces allow you to manage multiple packages within a single root package.json. This enables:
- Centralized dependency installation.
- Cross-referencing internal packages easily.
- Optimized disk space usage.
Workspace Hoisting Explained
A key feature of monorepo package managers is hoisting. Instead of installing the same external dependency multiple times in each project's node_modules folder, it's 'hoisted' to the root node_modules.
This means:
- Less disk space used.
- Faster installation times.
- Ensures all projects use the same version of a hoisted dependency, reducing potential conflicts.
Setting Up npm Workspaces
Let's see how to configure npm workspaces. You define them in the root package.json file.
Here, we tell npm to look for packages in the packages/* directory. Each sub-directory will contain its own package.json.
{
"name": "my-monorepo",
"version": "1.0.0",
"private": true,
"workspaces": [
"packages/*"
],
"scripts": {
"install:all": "npm install"
}
}Using Internal & External Dependencies
Now, let's create a simple ui-lib and an app project inside our packages/ folder. The app will depend on ui-lib and an external library, lodash.
Notice how ui-lib is referenced by its package name in app/package.json.
/* packages/ui-lib/package.json */
{
"name": "ui-lib",
"version": "1.0.0",
"main": "index.js"
}
/* packages/ui-lib/index.js */
export const Button = () => 'Monorepo Button';
/* packages/app/package.json */
{
"name": "app",
"version": "1.0.0",
"dependencies": {
"ui-lib": "*",
"lodash": "^4.17.21"
}
}
/* packages/app/index.js */
import { Button } from 'ui-lib';
import { capitalize } from 'lodash';
console.log(capitalize(Button()));
// Run 'npm install' from root, then 'node packages/app/index.js'Managing Version Conflicts
What if one project needs lodash@3.x and another needs lodash@4.x?
Monorepo tools often try to hoist a single version. If different versions are specified, some package managers might install multiple versions or require explicit overrides.
Best practice: Aim for a single, consistent version of major external dependencies across the entire monorepo to avoid complex resolution issues and ensure compatibility.
Dependency Graph & Tools
As monorepos grow, understanding the relationships between projects becomes crucial. A dependency graph visually maps out which projects depend on which.
Tools like Nx, Lerna, and Turborepo generate these graphs, helping you:
- Identify critical paths.
- Understand the impact of changes.
- Optimize build processes by only rebuilding affected projects.
Quick Check: Monorepo Dependencies
Consider a monorepo using npm workspaces with multiple projects. Which of the following statements about dependency management are true?
Recap: Monorepo Dependency Mastery
You've learned the essentials of dependency management in monorepos!
- Internal dependencies foster code sharing and consistency.
- External dependencies are managed efficiently using workspace features.
- Workspaces and hoisting optimize installation, disk space, and version consistency.
- Understanding the dependency graph is key for large monorepos.
Mastering these techniques is vital for building scalable and maintainable monorepo projects.
Frequently asked questions
Is the “Dependency Management in Monorepos” lesson free?
Yes — the full text of “Dependency Management in Monorepos” is free to read here on the web, and the Git Advanced: Monorepo, Submodules & Workflows course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Git Advanced: Monorepo, Submodules & Workflows course, upgrade to CoddyKit PRO.
What will I learn in “Dependency Management in Monorepos”?
Explore techniques for managing internal and external dependencies across multiple projects within a monorepo. You practise Git Advanced: Monorepo, Submodules & Workflows with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Git Advanced: Monorepo, Submodules & Workflows?
No prior experience is required. Git Advanced: Monorepo, Submodules & Workflows on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Dependency Management in Monorepos” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Git Advanced: Monorepo, Submodules & Workflows lesson?
Yes. Every Git Advanced: Monorepo, Submodules & Workflows lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Dependency Management in Monorepos
- Atomic Commits and Cross-Project Changes
- Monorepo CI/CD Strategies
- Build Caching and Affected-Only Builds