From 1fd361cbbec5a7ea0b2833d2af3c9b693df0e35c Mon Sep 17 00:00:00 2001 From: Theo Ephraim Date: Fri, 22 Nov 2024 13:59:16 -0800 Subject: [PATCH] add workspace tool links --- .../docs-site/src/content/docs/docs/guides/monorepos.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/packages/docs-site/src/content/docs/docs/guides/monorepos.mdx b/packages/docs-site/src/content/docs/docs/guides/monorepos.mdx index d0b9ef4a..241b260c 100644 --- a/packages/docs-site/src/content/docs/docs/guides/monorepos.mdx +++ b/packages/docs-site/src/content/docs/docs/guides/monorepos.mdx @@ -32,9 +32,9 @@ By default, DMNO will rely on your existing tooling to detect where potential ch | Workspace tool | Globs location | |---|---| -| npm, yarn, bun | `package.json`
└ `workspaces` | -| pnpm | `pnpm-workspace.yaml`
└ `packages` | -| moonrepo | `.moon/workspace.yml`
└ `projects` | +| [npm](https://docs.npmjs.com/cli/v8/using-npm/workspaces), [yarn](https://yarnpkg.com/features/workspaces#how-are-workspaces-declared), [bun](https://bun.sh/docs/install/workspaces) | `package.json`
└ `workspaces` | +| [pnpm](https://pnpm.io/workspaces) | `pnpm-workspace.yaml`
└ `packages` | +| [moonrepo](https://moonrepo.dev/docs/config/workspace#projects) | `.moon/workspace.yml`
└ `projects` | In some situations, like in a large polyglot repo, or a large repo that has multiple smaller monorepos within it, you may need an alternate way of defining where to look for DMNO services. In this case, you can create a `workspace.yaml` in your workspace root's `.dmno` folder. If this file is found, it will override everything else. @@ -57,7 +57,7 @@ To solve this, [`dmno run`](/docs/reference/cli/run/) boots up a server that oth :::tip[Env var pass-through] We use an injected `DMNO_PARENT_SERVER` env var to detect the parent server, so it must be passed through to child processes. -In [turborepo "strict mode"](https://turbo.build/repo/docs/crafting-your-repository/using-environment-variables#strict-mode), env vars are not all passed through by default. We must explicitly tell turbo about it using the [`globalPassThroughEnv`](https://turbo.build/repo/docs/reference/configuration#globalpassthroughenv) setting. For example: +In [Turborepo "strict mode"](https://turbo.build/repo/docs/crafting-your-repository/using-environment-variables#strict-mode), env vars are not all passed through by default. We must explicitly tell turbo about it using the [`globalPassThroughEnv`](https://turbo.build/repo/docs/reference/configuration#globalpassthroughenv) setting. For example: ```diff lang=json title='turbo.json' {