Repository: vercel/turborepo
Pull request #10455: docs: add workspace configuration example to package.json
Author: login: Feli-dev
Labels: name: area: docs
description: Improvements or additions to documentation
Created: 2025-05-07T19:49:05Z | Merged: 2025-05-09T16:56:10Z

## Description
This PR updates the package.json configuration example in the documentation to include the `workspaces` field, which is necessary for multi-package repositories using Turborepo.

## Motivation
While following this documentation page, I noticed that the package.json example showed how to add the `packageManager` field, but omitted the `workspaces` field. Although this information is later explained at https://turborepo.com/docs/crafting-your-repository/structuring-a-repository#declaring-directories-for-packages, including it in this initial example would make the documentation more consistent and help prevent confusion for new users who are following the steps sequentially.

## Changes made
I've updated the diff example in the "Add a `packageManager` field to root `package.json`" section to show the `workspaces` field alongside the `packageManager` field, making the example complete and consistent with what's explained later in the documentation.


Diff:
diff --git a/docs/site/content/docs/crafting-your-repository/structuring-a-repository.mdx b/docs/site/content/docs/crafting-your-repository/structuring-a-repository.mdx
index d636b19cd3759..63e3c2b80873b 100644
--- a/docs/site/content/docs/crafting-your-repository/structuring-a-repository.mdx
+++ b/docs/site/content/docs/crafting-your-repository/structuring-a-repository.mdx
@@ -216,7 +216,7 @@ First, your package manager needs to describe the locations of your packages. We
   }
   ```
 
-  <LinkToDocumentation href="https://bun.sh/docs/install/workspaces">npm workspace documentation</LinkToDocumentation>
+  <LinkToDocumentation href="https://bun.sh/docs/install/workspaces">bun workspace documentation</LinkToDocumentation>
   </Tab>
 
 </PackageManagerTabs>
diff --git a/docs/site/content/docs/getting-started/add-to-existing-repository.mdx b/docs/site/content/docs/getting-started/add-to-existing-repository.mdx
index 4a1a5b1d3c19e..4674df7a7760d 100644
--- a/docs/site/content/docs/getting-started/add-to-existing-repository.mdx
+++ b/docs/site/content/docs/getting-started/add-to-existing-repository.mdx
@@ -3,9 +3,10 @@ title: Add to an existing repository
 description: Using Turborepo with your existing repository
 ---
 
-import { Tabs, Tab } from '#components/tabs';
+import { PackageManagerTabs, Tabs, Tab } from '#components/tabs';
 import { Callout } from '#components/callout';
 import { Step, Steps } from '#components/steps';
+import { LinkToDocumentation } from '#components/link-to-documentation';
 
 Turborepo can be incrementally adopted in **any repository, single or multi-package**, to speed up the developer and CI workflows of the repository.
 
@@ -197,6 +198,74 @@ Turborepo optimizes your repository using information from your package manager.
   yet.
 </Callout>
 
+</Step>
+<Step>
+### Set up package manager workspaces
+
+For [multi-package workspaces](https://vercel.com/docs/glossary#multi-package-workspace), you'll need to configure your package manager to recognize your workspace structure.
+
+The `workspaces` field tells your package manager which directories contain your packages. Common patterns include `apps/*` for applications and `packages/*` for shared libraries.
+
+<Callout type="good-to-know">
+  If you're working with a single-package repository, you can skip this step as
+  workspaces aren't needed.
+</Callout>
+
+<PackageManagerTabs>
+
+  <Tab value="pnpm">
+  ```json title="pnpm-workspace.yaml"
+ packages:
+    - "apps/*"
+    - "packages/*"
+  ```
+  <LinkToDocumentation href="https://pnpm.io/pnpm-workspace_yaml">pnpm workspace documentation</LinkToDocumentation>
+
+  </Tab>
+
+  <Tab value="yarn">
+  ```json title="./package.json"
+  {
+    "workspaces": [
+      "apps/*",
+      "packages/*"
+    ]
+  }
+  ```
+
+  <LinkToDocumentation href="https://yarnpkg.com/features/workspaces#how-are-workspaces-declared">yarn workspace documentation</LinkToDocumentation>
+   </Tab>
+
+  <Tab value="npm">
+  ```json title="./package.json"
+  {
+    "workspaces": [
+      "apps/*",
+      "packages/*"
+    ]
+  }
+  ```
+
+  <LinkToDocumentation href="https://docs.npmjs.com/cli/v7/using-npm/workspaces#defining-workspaces">npm workspace documentation</LinkToDocumentation>
+  </Tab>
+
+  <Tab value="bun (Beta)">
+  ```json title="./package.json"
+  {
+    "workspaces": [
+      "apps/*",
+      "packages/*"
+    ]
+  }
+  ```
+
+  <LinkToDocumentation href="https://bun.sh/docs/install/workspaces">bun workspace documentation</LinkToDocumentation>
+  </Tab>
+
+</PackageManagerTabs>
+
+For more details on how to structure your repository, see [Structuring a Repository](/docs/crafting-your-repository/structuring-a-repository#declaring-directories-for-packages).
+
 </Step>
 <Step>
 ### Run tasks with `turbo`


Reviews:
user: login: anthonyshew
body: Good catch. This need is talked about elsewhere on the page, but an optional step wouldn't hurt.

Would it be possible that you could add another step to the flow instead of adding to this diff? Maybe titled "Set up package manager workspaces". And with a small explanation and then the diff.
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-07T19:55:44Z
user: login: anthonyshew
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-08T14:31:02Z
user: login: anthonyshew
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-08T14:31:32Z
user: login: anthonyshew
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-08T14:32:43Z
user: login: anthonyshew
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-08T14:34:34Z
user: login: anthonyshew
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-08T14:35:15Z
user: login: anthonyshew
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-08T14:35:31Z
user: login: anthonyshew
body: Thanks for the updates! Definitely the right direction. Getting into the details of things now.

I suspect we might have one more review round after we see how these look, but we're certainly close.
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-08T14:36:24Z
user: login: Feli-dev
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-08T19:24:35Z
user: login: Feli-dev
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-08T19:24:37Z
user: login: Feli-dev
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-08T19:24:39Z
user: login: Feli-dev
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-08T19:24:40Z
user: login: anthonyshew
body: Looks great. Thanks!
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-05-09T16:38:01Z

Review comments:
diff_hunk: @@ -197,6 +198,86 @@ Turborepo optimizes your repository using information from your package manager.
   yet.
 </Callout>
 
+</Step>
+<Step>
+### Set up package manager workspaces
+
+For multi-package repositories, you'll need to configure your package manager to recognize your workspace structure. This is done by adding a `workspaces` field to your root `package.json`.
path: docs/site/content/docs/getting-started/add-to-existing-repository.mdx
user: login: anthonyshew
body: Let's make "multi-package repositories" a link to https://vercel.com/docs/glossary#multi-package-workspace and have the copy be "multi-package workspaces".
created_at: 2025-05-08T14:31:01Z
author_association: CONTRIBUTOR
diff_hunk: @@ -197,6 +198,86 @@ Turborepo optimizes your repository using information from your package manager.
   yet.
 </Callout>
 
+</Step>
+<Step>
+### Set up package manager workspaces
+
+For multi-package repositories, you'll need to configure your package manager to recognize your workspace structure. This is done by adding a `workspaces` field to your root `package.json`.
path: docs/site/content/docs/getting-started/add-to-existing-repository.mdx
user: login: anthonyshew
body: Additionally, let's remove this sentence, since pnpm is different.
```suggestion
For multi-package repositories, you'll need to configure your package manager to recognize your workspace structure.
```
created_at: 2025-05-08T14:31:32Z
author_association: CONTRIBUTOR
diff_hunk: @@ -197,6 +198,86 @@ Turborepo optimizes your repository using information from your package manager.
   yet.
 </Callout>
 
+</Step>
+<Step>
+### Set up package manager workspaces
+
+For multi-package repositories, you'll need to configure your package manager to recognize your workspace structure. This is done by adding a `workspaces` field to your root `package.json`.
+
+The `workspaces` field tells your package manager which directories contain your packages. Common patterns include `apps/*` for applications and `packages/*` for shared libraries.
+
+```diff title="package.json"
+{
+  "packageManager": "npm@8.5.0",
++  "workspaces": [
++    "apps/*",
++    "packages/*"
++  ]
+}
+```
path: docs/site/content/docs/getting-started/add-to-existing-repository.mdx
user: login: anthonyshew
body: We can delete this diff since we're showing these codeblocks in the <PackageManagerTabs> anyway, and they'll be contextual to the user.
created_at: 2025-05-08T14:32:42Z
author_association: CONTRIBUTOR
diff_hunk: @@ -197,6 +198,86 @@ Turborepo optimizes your repository using information from your package manager.
   yet.
 </Callout>
 
+</Step>
+<Step>
+### Set up package manager workspaces
+
+For multi-package repositories, you'll need to configure your package manager to recognize your workspace structure. This is done by adding a `workspaces` field to your root `package.json`.
+
+The `workspaces` field tells your package manager which directories contain your packages. Common patterns include `apps/*` for applications and `packages/*` for shared libraries.
+
+```diff title="package.json"
+{
+  "packageManager": "npm@8.5.0",
++  "workspaces": [
++    "apps/*",
++    "packages/*"
++  ]
+}
+```
+
+<Callout type="info">
path: docs/site/content/docs/getting-started/add-to-existing-repository.mdx
user: login: anthonyshew
body: This is softens the rendered styles of the callout so it demands less attention. This is likely my personal preference, `info` makes sense, too, but I'm sensing that we can turn down the intent for this particular piece of knowledge.

```suggestion
<Callout type="good-to-know">
```
created_at: 2025-05-08T14:34:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -197,6 +198,86 @@ Turborepo optimizes your repository using information from your package manager.
   yet.
 </Callout>
 
+</Step>
+<Step>
+### Set up package manager workspaces
+
+For multi-package repositories, you'll need to configure your package manager to recognize your workspace structure. This is done by adding a `workspaces` field to your root `package.json`.
+
+The `workspaces` field tells your package manager which directories contain your packages. Common patterns include `apps/*` for applications and `packages/*` for shared libraries.
+
+```diff title="package.json"
+{
+  "packageManager": "npm@8.5.0",
++  "workspaces": [
++    "apps/*",
++    "packages/*"
++  ]
+}
+```
+
+<Callout type="info">
+  If you're working with a single-package repository, you can skip this step as
+  workspaces aren't needed.
+</Callout>
+
+Different package managers may have alternative ways to configure workspaces:
path: docs/site/content/docs/getting-started/add-to-existing-repository.mdx
user: login: anthonyshew
body: We can remove this line. The tabs construct conveys this without needing to say it explicitly.
created_at: 2025-05-08T14:35:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -197,6 +198,86 @@ Turborepo optimizes your repository using information from your package manager.
   yet.
 </Callout>
 
+</Step>
+<Step>
+### Set up package manager workspaces
+
+For multi-package repositories, you'll need to configure your package manager to recognize your workspace structure. This is done by adding a `workspaces` field to your root `package.json`.
+
+The `workspaces` field tells your package manager which directories contain your packages. Common patterns include `apps/*` for applications and `packages/*` for shared libraries.
+
+```diff title="package.json"
+{
+  "packageManager": "npm@8.5.0",
++  "workspaces": [
++    "apps/*",
++    "packages/*"
++  ]
+}
+```
+
+<Callout type="info">
+  If you're working with a single-package repository, you can skip this step as
+  workspaces aren't needed.
+</Callout>
+
+Different package managers may have alternative ways to configure workspaces:
+
+<PackageManagerTabs>
+
+  <Tab value="pnpm">
+  ```json title="pnpm-workspace.yaml"
+ packages:
+    - "apps/*"
+    - "packages/*"
+  ```
+  <LinkToDocumentation href="https://pnpm.io/pnpm-workspace_yaml">pnpm workspace documentation</LinkToDocumentation>
+
+  </Tab>
+
+  <Tab value="yarn">
+  ```json title="./package.json"
+  {
+    "workspaces": [
+      "apps/*",
+      "packages/*"
+    ]
+  }
+  ```
+
+  <LinkToDocumentation href="https://yarnpkg.com/features/workspaces#how-are-workspaces-declared">yarn workspace documentation</LinkToDocumentation>
+   </Tab>
+
+  <Tab value="npm">
+  ```json title="./package.json"
+  {
+    "workspaces": [
+      "apps/*",
+      "packages/*"
+    ]
+  }
+  ```
+
+  <LinkToDocumentation href="https://docs.npmjs.com/cli/v7/using-npm/workspaces#defining-workspaces">npm workspace documentation</LinkToDocumentation>
+  </Tab>
+
+  <Tab value="bun (Beta)">
+  ```json title="./package.json"
+  {
+    "workspaces": [
+      "apps/*",
+      "packages/*"
+    ]
+  }
+  ```
+
+  <LinkToDocumentation href="https://bun.sh/docs/install/workspaces">npm workspace documentation</LinkToDocumentation>
path: docs/site/content/docs/getting-started/add-to-existing-repository.mdx
user: login: anthonyshew
body: ```suggestion
  <LinkToDocumentation href="https://bun.sh/docs/install/workspaces">bun workspace documentation</LinkToDocumentation>
```
created_at: 2025-05-08T14:35:30Z
author_association: CONTRIBUTOR
diff_hunk: @@ -197,6 +198,86 @@ Turborepo optimizes your repository using information from your package manager.
   yet.
 </Callout>
 
+</Step>
+<Step>
+### Set up package manager workspaces
+
+For multi-package repositories, you'll need to configure your package manager to recognize your workspace structure. This is done by adding a `workspaces` field to your root `package.json`.
+
+The `workspaces` field tells your package manager which directories contain your packages. Common patterns include `apps/*` for applications and `packages/*` for shared libraries.
+
+```diff title="package.json"
+{
+  "packageManager": "npm@8.5.0",
++  "workspaces": [
++    "apps/*",
++    "packages/*"
++  ]
+}
+```
+
+<Callout type="info">
+  If you're working with a single-package repository, you can skip this step as
+  workspaces aren't needed.
+</Callout>
+
+Different package managers may have alternative ways to configure workspaces:
+
+<PackageManagerTabs>
+
+  <Tab value="pnpm">
+  ```json title="pnpm-workspace.yaml"
+ packages:
+    - "apps/*"
+    - "packages/*"
+  ```
+  <LinkToDocumentation href="https://pnpm.io/pnpm-workspace_yaml">pnpm workspace documentation</LinkToDocumentation>
+
+  </Tab>
+
+  <Tab value="yarn">
+  ```json title="./package.json"
+  {
+    "workspaces": [
+      "apps/*",
+      "packages/*"
+    ]
+  }
+  ```
+
+  <LinkToDocumentation href="https://yarnpkg.com/features/workspaces#how-are-workspaces-declared">yarn workspace documentation</LinkToDocumentation>
+   </Tab>
+
+  <Tab value="npm">
+  ```json title="./package.json"
+  {
+    "workspaces": [
+      "apps/*",
+      "packages/*"
+    ]
+  }
+  ```
+
+  <LinkToDocumentation href="https://docs.npmjs.com/cli/v7/using-npm/workspaces#defining-workspaces">npm workspace documentation</LinkToDocumentation>
+  </Tab>
+
+  <Tab value="bun (Beta)">
+  ```json title="./package.json"
+  {
+    "workspaces": [
+      "apps/*",
+      "packages/*"
+    ]
+  }
+  ```
+
+  <LinkToDocumentation href="https://bun.sh/docs/install/workspaces">npm workspace documentation</LinkToDocumentation>
path: docs/site/content/docs/getting-started/add-to-existing-repository.mdx
user: login: Feli-dev
body: ✔️ 
created_at: 2025-05-08T19:24:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -197,6 +198,86 @@ Turborepo optimizes your repository using information from your package manager.
   yet.
 </Callout>
 
+</Step>
+<Step>
+### Set up package manager workspaces
+
+For multi-package repositories, you'll need to configure your package manager to recognize your workspace structure. This is done by adding a `workspaces` field to your root `package.json`.
+
+The `workspaces` field tells your package manager which directories contain your packages. Common patterns include `apps/*` for applications and `packages/*` for shared libraries.
+
+```diff title="package.json"
+{
+  "packageManager": "npm@8.5.0",
++  "workspaces": [
++    "apps/*",
++    "packages/*"
++  ]
+}
+```
+
+<Callout type="info">
path: docs/site/content/docs/getting-started/add-to-existing-repository.mdx
user: login: Feli-dev
body: ✔️ 
created_at: 2025-05-08T19:24:37Z
author_association: CONTRIBUTOR
diff_hunk: @@ -197,6 +198,86 @@ Turborepo optimizes your repository using information from your package manager.
   yet.
 </Callout>
 
+</Step>
+<Step>
+### Set up package manager workspaces
+
+For multi-package repositories, you'll need to configure your package manager to recognize your workspace structure. This is done by adding a `workspaces` field to your root `package.json`.
+
+The `workspaces` field tells your package manager which directories contain your packages. Common patterns include `apps/*` for applications and `packages/*` for shared libraries.
+
+```diff title="package.json"
+{
+  "packageManager": "npm@8.5.0",
++  "workspaces": [
++    "apps/*",
++    "packages/*"
++  ]
+}
+```
path: docs/site/content/docs/getting-started/add-to-existing-repository.mdx
user: login: Feli-dev
body: ✔️ 
created_at: 2025-05-08T19:24:39Z
author_association: CONTRIBUTOR
diff_hunk: @@ -197,6 +198,86 @@ Turborepo optimizes your repository using information from your package manager.
   yet.
 </Callout>
 
+</Step>
+<Step>
+### Set up package manager workspaces
+
+For multi-package repositories, you'll need to configure your package manager to recognize your workspace structure. This is done by adding a `workspaces` field to your root `package.json`.
path: docs/site/content/docs/getting-started/add-to-existing-repository.mdx
user: login: Feli-dev
body: ✔️ 
created_at: 2025-05-08T19:24:40Z
author_association: CONTRIBUTOR

PR comments:
user: login: Feli-dev
created_at: 2025-05-07T19:49:12Z
body: I'm open to making any additional adjustments that might be necessary. Thank you for considering this contribution to improve documentation consistency.
author_association: CONTRIBUTOR
user: login: vercel[bot]
created_at: 2025-05-07T19:49:17Z
body: [vc]: #jvFJb3dOlMXS+R1GeLdTeOC2LMnLp3UrkVBOq3BcQA8=:eyJpc01vbm9yZXBvIjp0cnVlLCJ0eXBlIjoiZ2l0aHViIiwicHJvamVjdHMiOlt7Im5hbWUiOiJleGFtcGxlcy10YWlsd2luZC13ZWIiLCJyb290RGlyZWN0b3J5IjoiZXhhbXBsZXMvd2l0aC10YWlsd2luZC9hcHBzL3dlYiIsImluc3BlY3RvclVybCI6Imh0dHBzOi8vdmVyY2VsLmNvbS92ZXJjZWwvZXhhbXBsZXMtdGFpbHdpbmQtd2ViL0JmSjRZQWFFVTluZ1NMNFJIbWE5QkhjU0F2a1YiLCJwcmV2aWV3VXJsIjoiZXhhbXBsZXMtdGFpbHdpbmQtd2ViLWdpdC1mb3JrLWZlbGktZGV2LXBhdGNoLTEudmVyY2VsLnNoIiwibmV4dENvbW1pdFN0YXR1cyI6IkRFUExPWUVEIiwibGl2ZUZlZWRiYWNrIjp7InJlc29sdmVkIjowLCJ1bnJlc29sdmVkIjowLCJ0b3RhbCI6MCwibGluayI6ImV4YW1wbGVzLXRhaWx3aW5kLXdlYi1naXQtZm9yay1mZWxpLWRldi1wYXRjaC0xLnZlcmNlbC5zaCJ9fSx7Im5hbWUiOiJleGFtcGxlcy1uYXRpdmUtd2ViIiwicm9vdERpcmVjdG9yeSI6ImV4YW1wbGVzL3dpdGgtcmVhY3QtbmF0aXZlLXdlYi9hcHBzL3dlYiIsImluc3BlY3RvclVybCI6Imh0dHBzOi8vdmVyY2VsLmNvbS92ZXJjZWwvZXhhbXBsZXMtbmF0aXZlLXdlYi9IanJGa2hHU1RZdXFKYkdWWHFiYnU0a3NxTHFkIiwicHJldmlld1VybCI6ImV4YW1wbGVzLW5hdGl2ZS13ZWItZ2l0LWZvcmstZmVsaS1kZXYtcGF0Y2gtMS52ZXJjZWwuc2giLCJuZXh0Q29tbWl0U3RhdHVzIjoiREVQTE9ZRUQiLCJsaXZlRmVlZGJhY2siOnsicmVzb2x2ZWQiOjAsInVucmVzb2x2ZWQiOjAsInRvdGFsIjowLCJsaW5rIjoiZXhhbXBsZXMtbmF0aXZlLXdlYi1naXQtZm9yay1mZWxpLWRldi1wYXRjaC0xLnZlcmNlbC5zaCJ9fSx7Im5hbWUiOiJleGFtcGxlcy1iYXNpYy13ZWIiLCJyb290RGlyZWN0b3J5IjoiZXhhbXBsZXMvYmFzaWMvYXBwcy93ZWIiLCJpbnNwZWN0b3JVcmwiOiJodHRwczovL3ZlcmNlbC5jb20vdmVyY2VsL2V4YW1wbGVzLWJhc2ljLXdlYi84c3FNeGNDY3dSQlZwTlp2TEdQR3lETUV6bzNpIiwicHJldmlld1VybCI6ImV4YW1wbGVzLWJhc2ljLXdlYi1naXQtZm9yay1mZWxpLWRldi1wYXRjaC0xLnZlcmNlbC5zaCIsIm5leHRDb21taXRTdGF0dXMiOiJERVBMT1lFRCIsImxpdmVGZWVkYmFjayI6eyJyZXNvbHZlZCI6MCwidW5yZXNvbHZlZCI6MCwidG90YWwiOjAsImxpbmsiOiJleGFtcGxlcy1iYXNpYy13ZWItZ2l0LWZvcmstZmVsaS1kZXYtcGF0Y2gtMS52ZXJjZWwuc2gifX0seyJuYW1lIjoiZXhhbXBsZXMtdml0ZS13ZWIiLCJyb290RGlyZWN0b3J5IjoiZXhhbXBsZXMvd2l0aC12aXRlL2FwcHMvd2ViIiwiaW5zcGVjdG9yVXJsIjoiaHR0cHM6Ly92ZXJjZWwuY29tL3ZlcmNlbC9leGFtcGxlcy12aXRlLXdlYi9HZTdQTDROMTlKY1NUbTFxR3l2a0JuWnREZlBqIiwicHJldmlld1VybCI6ImV4YW1wbGVzLXZpdGUtd2ViLWdpdC1mb3JrLWZlbGktZGV2LXBhdGNoLTEudmVyY2VsLnNoIiwibmV4dENvbW1pdFN0YXR1cyI6IkRFUExPWUVEIiwibGl2ZUZlZWRiYWNrIjp7InJlc29sdmVkIjowLCJ1bnJlc29sdmVkIjowLCJ0b3RhbCI6MCwibGluayI6ImV4YW1wbGVzLXZpdGUtd2ViLWdpdC1mb3JrLWZlbGktZGV2LXBhdGNoLTEudmVyY2VsLnNoIn19LHsibmFtZSI6ImV4YW1wbGVzLWRlc2lnbnN5c3RlbS1kb2NzIiwicm9vdERpcmVjdG9yeSI6ImV4YW1wbGVzL2Rlc2lnbi1zeXN0ZW0vYXBwcy9kb2NzIiwiaW5zcGVjdG9yVXJsIjoiaHR0cHM6Ly92ZXJjZWwuY29tL3ZlcmNlbC9leGFtcGxlcy1kZXNpZ25zeXN0ZW0tZG9jcy82cDFwSGgyN283YmZiUnBMeHJHeG43eDVISDJ6IiwicHJldmlld1VybCI6ImV4YW1wbGVzLWRlc2lnbnN5c3RlbS1kb2NzLWdpdC1mb3JrLWZlbGktZGV2LXBhdGNoLTEudmVyY2VsLnNoIiwibmV4dENvbW1pdFN0YXR1cyI6IkRFUExPWUVEIiwibGl2ZUZlZWRiYWNrIjp7InJlc29sdmVkIjowLCJ1bnJlc29sdmVkIjowLCJ0b3RhbCI6MCwibGluayI6ImV4YW1wbGVzLWRlc2lnbnN5c3RlbS1kb2NzLWdpdC1mb3JrLWZlbGktZGV2LXBhdGNoLTEudmVyY2VsLnNoIn19LHsibmFtZSI6InR1cmJvLXNpdGUiLCJyb290RGlyZWN0b3J5IjoiZG9jcy9zaXRlIiwiaW5zcGVjdG9yVXJsIjoiaHR0cHM6Ly92ZXJjZWwuY29tL3ZlcmNlbC90dXJiby1zaXRlLzczOGg2TXR1akNyWEd4a3Y3S0hDZ0tiaFJ1ZngiLCJwcmV2aWV3VXJsIjoidHVyYm8tc2l0ZS1naXQtZm9yay1mZWxpLWRldi1wYXRjaC0xLnZlcmNlbC5zaCIsIm5leHRDb21taXRTdGF0dXMiOiJERVBMT1lFRCIsImxpdmVGZWVkYmFjayI6eyJyZXNvbHZlZCI6MCwidW5yZXNvbHZlZCI6MCwidG90YWwiOjAsImxpbmsiOiJ0dXJiby1zaXRlLWdpdC1mb3JrLWZlbGktZGV2LXBhdGNoLTEudmVyY2VsLnNoIn19LHsibmFtZSI6ImV4YW1wbGVzLXN2ZWx0ZS13ZWIiLCJyb290RGlyZWN0b3J5IjoiZXhhbXBsZXMvd2l0aC1zdmVsdGUvYXBwcy93ZWIiLCJpbnNwZWN0b3JVcmwiOiJodHRwczovL3ZlcmNlbC5jb20vdmVyY2VsL2V4YW1wbGVzLXN2ZWx0ZS13ZWIvRUpmQ0pIM2pzMlpkOVRkOXk4NWZtM0xlUHB1YyIsInByZXZpZXdVcmwiOiIiLCJuZXh0Q29tbWl0U3RhdHVzIjoiRkFJTEVEIiwibGl2ZUZlZWRiYWNrIjp7InJlc29sdmVkIjowLCJ1bnJlc29sdmVkIjowLCJ0b3RhbCI6MCwibGluayI6IiJ9fV19
**The latest updates on your projects**. Learn more about [Vercel for Git ↗︎](https://vercel.link/github-learn-more)

| Name | Status | Preview | Comments | Updated (UTC) |
| :--- | :----- | :------ | :------- | :------ |
| **examples-basic-web** | ✅ Ready ([Inspect](https://vercel.com/vercel/examples-basic-web/8sqMxcCcwRBVpNZvLGPGyDMEzo3i)) | [Visit Preview](https://examples-basic-web-git-fork-feli-dev-patch-1.vercel.sh) | 💬 [**Add feedback**](https://vercel.live/open-feedback/examples-basic-web-git-fork-feli-dev-patch-1.vercel.sh?via=pr-comment-feedback-link) | May 12, 2025 5:04pm |
| **examples-designsystem-docs** | ✅ Ready ([Inspect](https://vercel.com/vercel/examples-designsystem-docs/6p1pHh27o7bfbRpLxrGxn7x5HH2z)) | [Visit Preview](https://examples-designsystem-docs-git-fork-feli-dev-patch-1.vercel.sh) | 💬 [**Add feedback**](https://vercel.live/open-feedback/examples-designsystem-docs-git-fork-feli-dev-patch-1.vercel.sh?via=pr-comment-feedback-link) | May 12, 2025 5:04pm |
| **examples-native-web** | ✅ Ready ([Inspect](https://vercel.com/vercel/examples-native-web/HjrFkhGSTYuqJbGVXqbbu4ksqLqd)) | [Visit Preview](https://examples-native-web-git-fork-feli-dev-patch-1.vercel.sh) | 💬 [**Add feedback**](https://vercel.live/open-feedback/examples-native-web-git-fork-feli-dev-patch-1.vercel.sh?via=pr-comment-feedback-link) | May 12, 2025 5:04pm |
| **examples-svelte-web** | ❌ Failed ([Inspect](https://vercel.com/vercel/examples-svelte-web/EJfCJH3js2Zd9Td9y85fm3LePpuc)) |  |  | May 12, 2025 5:04pm |
| **examples-tailwind-web** | ✅ Ready ([Inspect](https://vercel.com/vercel/examples-tailwind-web/BfJ4YAaEU9ngSL4RHma9BHcSAvkV)) | [Visit Preview](https://examples-tailwind-web-git-fork-feli-dev-patch-1.vercel.sh) | 💬 [**Add feedback**](https://vercel.live/open-feedback/examples-tailwind-web-git-fork-feli-dev-patch-1.vercel.sh?via=pr-comment-feedback-link) | May 12, 2025 5:04pm |
| **examples-vite-web** | ✅ Ready ([Inspect](https://vercel.com/vercel/examples-vite-web/Ge7PL4N19JcSTm1qGyvkBnZtDfPj)) | [Visit Preview](https://examples-vite-web-git-fork-feli-dev-patch-1.vercel.sh) | 💬 [**Add feedback**](https://vercel.live/open-feedback/examples-vite-web-git-fork-feli-dev-patch-1.vercel.sh?via=pr-comment-feedback-link) | May 12, 2025 5:04pm |
| **turbo-site** | ✅ Ready ([Inspect](https://vercel.com/vercel/turbo-site/738h6MtujCrXGxkv7KHCgKbhRufx)) | [Visit Preview](https://turbo-site-git-fork-feli-dev-patch-1.vercel.sh) | 💬 [**Add feedback**](https://vercel.live/open-feedback/turbo-site-git-fork-feli-dev-patch-1.vercel.sh?via=pr-comment-feedback-link) | May 12, 2025 5:04pm |








author_association: CONTRIBUTOR
user: login: vercel[bot]
created_at: 2025-05-07T19:49:18Z
body: @Feli-dev is attempting to deploy a commit to the **Vercel** Team on [Vercel](https://vercel.com).

A member of the Team first needs to [authorize it](https://vercel.com/git/authorize?team=Vercel&type=github&job=%7B%22headInfo%22%3A%7B%22sha%22%3A%22da2e6ae9302fe8c07efa470ad68b2677952d107e%22%7D%2C%22id%22%3A%22QmQfgwpkBNNCWCVXzVy5PDtM6Bz2X9MeKuFchGt5x7ms6E%22%2C%22org%22%3A%22vercel%22%2C%22prId%22%3A10455%2C%22repo%22%3A%22turborepo%22%7D).


author_association: CONTRIBUTOR
user: login: Feli-dev
created_at: 2025-05-08T02:19:38Z
body: > Good catch. This need is talked about elsewhere on the page, but an optional step wouldn't hurt.
> 
> Would it be possible that you could add another step to the flow instead of adding to this diff? Maybe titled "Set up package manager workspaces". And with a small explanation and then the diff.

Thank you for the feedback! I've implemented the changes as suggested by adding a new dedicated step titled "Set up package manager workspaces" between the current steps 4 and 5.

The new step includes:
- A brief explanation of what workspaces are and why they're needed for multi-package repos
- The diff showing how to add the workspaces field to package.json
- Additional information for different package managers (npm, yarn, pnpm)
- A note that single-package repository users can skip this step
- A reference to the more detailed documentation

I've just pushed these changes to my branch. Please let me know if this addresses your suggestion or if you'd like to see any further adjustments.
author_association: CONTRIBUTOR
user: login: Feli-dev
created_at: 2025-05-09T16:40:20Z
body: > Looks great. Thanks!

Thank you for the guidance and review! 
Happy to contribute and glad the changes worked out well. Looking forward to the merge. 🚀 
author_association: CONTRIBUTOR