这是indexloc提供的服务，不要输入任何密码
Skip to content

docs: added pnpm catalogs #10463

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 9, 2025
Merged

docs: added pnpm catalogs #10463

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6aeb93d
docs: added pnpm catalogs.mdx
mrr11k May 9, 2025
fbdb44d
Edits.
anthonyshew May 9, 2025
0fb396d
WIP 502a7
anthonyshew May 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion docs/site/content/docs/crafting-your-repository/managing-dependencies.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -180,10 +180,12 @@ You can use your package manager to update dependency versions in one command.
<PackageManagerTabs>

<Tab value="pnpm">

```bash title="Terminal"
pnpm up --recursive typescript@latest
```
<small>[→ pnpm documentation](https://pnpm.io/cli/update#--recursive--r)</small>

<small>[→ pnpm documentation](https://pnpm.io/cli/update#--recursive--r)</small>

</Tab>

Expand Down Expand Up @@ -220,6 +222,12 @@ No equivalent
</Tab>
</PackageManagerTabs>

#### pnpm catalogs

In pnpm v9.5+, you can use catalogs to define dependency version ranges as reusable constants. This will keep dependencies on the same version since you're referencing the same value across the workspace.

To learn more, [visit the pnpm catalogs documentation](https://pnpm.io/catalogs).

#### Using an IDE

Your IDE's refactoring tooling can find and replace the version of a dependency across all `package.json` files in your repository at once. Try using a regex like `"next": ".*"` on `package.json` files to find all instances of the `next` package and replace them with the version you want. When you're done, make sure to run your package manager's install command to update your lockfile.
Expand Down
Loading