Skip to content

Commit 6d40e9b

Browse files
cylewaitforitgraphite-app[bot]jaysoo
authored andcommitted
docs(core): add Yarn catalog to dependency management (#34874)
<!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Adds references to [Yarn catalog](https://yarnpkg.com/features/catalogs) to dependency management documentation. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Related #34377 --------- Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
1 parent 738e3cb commit 6d40e9b

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

astro-docs/src/content/docs/concepts/Decisions/dependency-management.mdoc

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,8 +45,10 @@ For building and deployment, you'll need to ensure each project only includes it
4545

4646
The main challenge with this approach is coordinating dependency updates across independent teams. When multiple teams work on different, or even the same, applications within the same repo, they need to align on dependency upgrades. While this requires more coordination, it often results in less total work - upgrading a dependency once across all projects is typically more efficient than managing multiple separate upgrades over time.
4747

48-
{% aside type="tip" title="PNPM Catalog Support" %}
49-
When using PNPM, use [PNPM catalogs](https://pnpm.io/catalogs) to maintain single version policy. Define versions in `pnpm-workspace.yaml` and reference them as `"<package>": "catalog:"` in project `package.json` files (Nx 22+).
48+
{% aside type="tip" title="Dependency Catalog Support" %}
49+
50+
When using pnpm or Yarn, use [pnpm catalogs](https://pnpm.io/catalogs) or [Yarn catalogs](https://yarnpkg.com/features/catalogs) to maintain single version policy. Define versions in `pnpm-workspace.yaml` or `.yarnrc.yml` respectively and reference them as `"<package>": "catalog:"` in project `package.json` files (Nx 22+ for pnpm and Nx 22.6+ for Yarn).
51+
5052
{% /aside %}
5153

5254
**Pros:**

0 commit comments

Comments
 (0)