Skip to content

chore: use pnpm catalogs#970

Open
PatrykWalach wants to merge 1 commit intoisographlabs:mainfrom
PatrykWalach:pnpm-catalogs
Open

chore: use pnpm catalogs#970
PatrykWalach wants to merge 1 commit intoisographlabs:mainfrom
PatrykWalach:pnpm-catalogs

Conversation

@PatrykWalach
Copy link
Member

@PatrykWalach PatrykWalach commented Mar 1, 2026

https://pnpm.io/catalogs#advantages

In a workspace (i.e. monorepo or multi-package repo) it's common for the same dependency to be used by many packages. Catalogs reduce duplication when authoring package.json files and provide a few benefits in doing so:

  • Maintain unique versions — It's usually desirable to have only one version of a dependency in a workspace. Catalogs make this easier to maintain. Duplicated dependencies can conflict at runtime and cause bugs. Duplicates also increase size when using a bundler.
  • Easier upgrades — When upgrading a dependency, only the catalog entry in pnpm-workspace.yaml needs to be edited rather than all package.json files using that dependency. This saves time — only one line needs to be changed instead of many.
  • Fewer merge conflicts — Since package.json files do not need to be edited when upgrading a dependency, git merge conflicts no longer happen in these files.

https://pnpm.io/catalogs#advantages

In a workspace (i.e. monorepo or multi-package repo) it's common for the
same dependency to be used by many packages. Catalogs reduce duplication
when authoring package.json files and provide a few benefits in doing
so:    Maintain unique versions — It's usually desirable to have only
one version of a dependency in a workspace. Catalogs make this easier to
maintain. Duplicated dependencies can conflict at runtime and cause
bugs. Duplicates also increase size when using a bundler.    Easier
upgrades — When upgrading a dependency, only the catalog entry in
pnpm-workspace.yaml needs to be edited rather than all package.json
files using that dependency. This saves time — only one line needs to be
changed instead of many.    Fewer merge conflicts — Since package.json
files do not need to be edited when upgrading a dependency, git merge
conflicts no longer happen in these files.
@PatrykWalach PatrykWalach marked this pull request as ready for review March 1, 2026 15:27
@PatrykWalach PatrykWalach changed the title use pnpm catalogs chore: use pnpm catalogs Mar 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant