docs(nx-dev): add monorepo myths article #32944
Open
+167
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
View your CI Pipeline Execution ↗ for commit 11e9bd3
☁️ Nx Cloud last updated this comment at |
![nx-cloud[bot]](https://avatars.githubusercontent.com/in/80458?s=60&v=4){kind=small}
There was a problem hiding this comment.
Nx Cloud is proposing a fix for your failed CI:
We've corrected the internal documentation links in the monorepo myths blog post. The links now point to the correct URL paths (/ci/features/affected instead of /features/ci-features/affected, /recipes/adopting-nx/* instead of /guides/adopting-nx/*, and /features/enhance-AI with proper capitalization). This fixes the internal link checker failures.
We verified this fix by re-running nx-dev:build.
Suggested Fix changes
diff --git a/docs/blog/2025-10-02-monorepo-myths.md b/docs/blog/2025-10-02-monorepo-myths.md
index a2ae5a8dc4..630eda7376 100644
--- a/docs/blog/2025-10-02-monorepo-myths.md
+++ b/docs/blog/2025-10-02-monorepo-myths.md
@@ -35,7 +35,7 @@ In fact, monorepos actually encourage [modular architecture](/blog/virtuous-cycl
This myth stems from traditional systems that lack dependency awareness. Without understanding what's affected by a change, you're forced to rebuild and retest everything, leading to multi-hour pipelines and nightly tests.
-**The Reality**: Modern monorepo tools provide [dependency graphs](/features/explore-graph) that expose exactly what's been affected by your changes. You can [filter work to only the subset of projects](/features/ci-features/affected) that actually need attention.
+**The Reality**: Modern monorepo tools provide [dependency graphs](/features/explore-graph) that expose exactly what's been affected by your changes. You can [filter work to only the subset of projects](/ci/features/affected) that actually need attention.
CI cost and performance depend primarily on pipeline design, not repository topology. With proper dependency handling and features like [caching](/concepts/how-caching-works), monorepos can actually be faster and cheaper than polyrepos, especially when you're only running the subset of work that's truly necessary.
@@ -67,7 +67,7 @@ For example, the Nx codebase contains TypeScript, Rust, Go, Kotlin, and Python.
This assumption comes from painful memories of technology migrations (anyone remember AngularJS to Angular 2?).
-**The Reality**: Migrating to monorepos doesn't have to be a big bang. Start with a single repo, turn on monorepo tooling, then [import another repository while preserving the full Git history](/guides/adopting-nx/import-project). Initially, treat them as separate repositories that happen to be collocated in the same Git repository.
+**The Reality**: Migrating to monorepos doesn't have to be a big bang. Start with a single repo, turn on monorepo tooling, then [import another repository while preserving the full Git history](/recipes/adopting-nx/import-project). Initially, treat them as separate repositories that happen to be collocated in the same Git repository.
As you add more pieces (shared libraries, services, etc.), you can gradually think about standardization, alignment, and creating joint pipelines. You don't have to place everything in the same monorepo immediately. Features like [Polygraph](/blog/nx-cloud-introducing-polygraph) allow you to see dependencies beyond single monorepo borders and run checks across several repositories as if they were one.
@@ -79,8 +79,8 @@ Lockstep versioning means deploying everything simultaneously with aligned versi
Workspace-aware package managers and monorepo tools often include release tooling that enables you to:
-- [Publish package versions independently](/guides/nx-release/release-projects-independently)
-- [Handle changelogs per project](/guides/nx-release/configure-changelog-format)
+- [Publish package versions independently](/recipes/nx-release/release-projects-independently)
+- [Handle changelogs per project](/recipes/nx-release/configure-changelog-format)
You can implement continuous deployment where you deploy on every change, or decide when to deploy on a per-project, per-application basis.
@@ -139,7 +139,7 @@ Monorepo tools [share valuable context with AI](/getting-started/ai-integration)
- Conventions for the codebase
- How to run tasks to validate changes
-Learn more about [making your AI assistant smarter with Nx](/features/enhance-ai) and watch our [webinar on AI-assisted development in monorepos](https://go.nx.dev/april2025-webinar).
+Learn more about [making your AI assistant smarter with Nx](/features/enhance-AI) and watch our [webinar on AI-assisted development in monorepos](https://go.nx.dev/april2025-webinar).
## The Path Forward
✅ The fix was applied locally and will need to be manually pushed to this branch.
⚙️ An Nx Cloud workspace admin can disable these reviews in workspace settings.
philipjfulcher
force-pushed
the
philip/monorepo-myths
branch
from
a1f78cb to
11e9bd3
Compare
juristr
approved these changes
Oct 28, 2025
|
|
||
| "We'd love to adopt a monorepo, but we just don't have time to block weeks or months of development for a full migration." | ||
|
|
||
| This assumption comes from painful memories of technology migrations (anyone remember AngularJS to Angular 2?). |
There was a problem hiding this comment.
Is this still a valid reference point 🤔. (like AngularJS => Angular) 😅
|
|
||
| You can still make overrides when needed. If a legacy application needs to use a different version of React or Java, you can override it per project without affecting the rest of your monorepo. | ||
|
|
||
| ## Myth #10: AI Doesn't Work in Large Codebases |
There was a problem hiding this comment.
If we wanted we could also point to monorepo.tools/ai
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.