From 88eeee78088047b37f0c81343d97c20977998c07 Mon Sep 17 00:00:00 2001 From: Anthony Shew Date: Mon, 9 Dec 2024 16:10:38 -0700 Subject: [PATCH] docs: provide reasoning on why Turborepo doesn't support nested workspaces (#9586) --- .../crafting-your-repository/structuring-a-repository.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/repo-docs/crafting-your-repository/structuring-a-repository.mdx b/docs/repo-docs/crafting-your-repository/structuring-a-repository.mdx index bbc03d3081783..6558cd1a96d11 100644 --- a/docs/repo-docs/crafting-your-repository/structuring-a-repository.mdx +++ b/docs/repo-docs/crafting-your-repository/structuring-a-repository.mdx @@ -155,7 +155,7 @@ First, your package manager needs to describe the locations of your packages. We Using this configuration, every directory **with a `package.json`** in the `apps` or `packages` directories will be considered a package. -Turborepo does not support nested packages like `apps/**` or `packages/**`. Using a structure that would put a package at `apps/a` and another at `apps/a/b` will result in an error. +Turborepo does not support nested packages like `apps/**` or `packages/**` due to ambiguous behavior among package managers in the JavaScript ecosystem. Using a structure that would put a package at `apps/a` and another at `apps/a/b` will result in an error. If you'd like to group packages by directory, you can do this using globs like `packages/*` and `packages/group/*` and **not** creating a `packages/group/package.json` file.