Catalogs are a useful feature of pnpm which allow you to link many packages to a set of versions which you control in a centralised place.
Here’s an example for prisma:
In package.json: "dependencies”: { “@prisma/client”: “catalog:prisma” } then in your pnpm-workspaces.yaml you setup as such (this example for prisma):
```
catalogs:
prisma:
‘@prisma/client’: 6.6.0
```
This is particularly useful for trigger.dev, for example in my case I have 12 sub packages each which should refer to the same trigger.dev version.
The cli currently handles the case where the packages are defined as individual versions and helpfully offers to update them all to match the latest. However it doesn’t support catalogs, which need to be updated in the pnpm-workspace.yaml instead of each package.json file.
I think it should support this too for the cli :)
In Review
💡 Feature Request
10 months ago

Andy
Get notified by email when there are changes.
In Review
💡 Feature Request
10 months ago

Andy
Get notified by email when there are changes.