From f1732724c9b83ed17013b5d5e79f15056c705a67 Mon Sep 17 00:00:00 2001 From: Lorenzo Zabot Date: Sat, 17 May 2025 14:21:52 +0200 Subject: [PATCH] docs: GitHub -> Git --- content/cli/workspaces.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/cli/workspaces.md b/content/cli/workspaces.md index cdf0b49c..930dacba 100644 --- a/content/cli/workspaces.md +++ b/content/cli/workspaces.md @@ -3,7 +3,7 @@ Nest has two modes for organizing code: - **standard mode**: useful for building individual project-focused applications that have their own dependencies and settings, and don't need to optimize for sharing modules, or optimizing complex builds. This is the default mode. -- **monorepo mode**: this mode treats code artifacts as part of a lightweight **monorepo**, and may be more appropriate for teams of developers and/or multi-project environments. It automates parts of the build process to make it easy to create and compose modular components, promotes code re-use, makes integration testing easier, makes it easy to share project-wide artifacts like `eslint` rules and other configuration policies, and is easier to use than alternatives like GitHub submodules. Monorepo mode employs the concept of a **workspace**, represented in the `nest-cli.json` file, to coordinate the relationship between the components of the monorepo. +- **monorepo mode**: this mode treats code artifacts as part of a lightweight **monorepo**, and may be more appropriate for teams of developers and/or multi-project environments. It automates parts of the build process to make it easy to create and compose modular components, promotes code re-use, makes integration testing easier, makes it easy to share project-wide artifacts like `eslint` rules and other configuration policies, and is easier to use than alternatives like Git submodules. Monorepo mode employs the concept of a **workspace**, represented in the `nest-cli.json` file, to coordinate the relationship between the components of the monorepo. It's important to note that virtually all of Nest's features are independent of your code organization mode. The **only** effect of this choice is how your projects are composed and how build artifacts are generated. All other functionality, from the CLI to core modules to add-on modules work the same in either mode.