[code-infra] Adopt pnpm `catalog:` feature

[oliviertassinari]

Summary

This was first introduced in mui/mui-x#18302. It looks like it would be positive for us, enforcing that npm versions that must be the same, stay the same.

For example, @babel/runtime using during runtime and @babel/plugin-transform-runtime used during build need to match, we can make @babel/runtime the same a cross all packaged, and in the PR review make an update of a version show new to the value or @babel/plugin-transform-runtime.

Also, it looks like we could go back to mui/mui-x#18302 and remove the dev dependencies defined at the package level multiple times, to move them to the root package.json. Or at least, I'm confused about it mui/base-ui#2801 (comment).

Examples

No response

Motivation

No response

Search keywords: -

[Janpot]

Adopt pnpm catalog: feature

My main objection to this is that it's not really adopted by other package managers. These sort of features tend to be buggy and some tooling may not integrate well with it (thinking of pkg.pr.new in the past). We also already had to build some special cases in code infra tooling to fix issues around it.

For example, @babel/runtime using during runtime and @babel/plugin-transform-runtime used during build need to match

The build tooling already knows how to do this correctly without the need for catalog:.

Personally, I lean slightly more towards linting for consistency than towards catalogs:, until more package managers adopt this protocol.

[oliviertassinari]

I lean slightly more towards linting for consistency than towards catalogs:, until more package managers adopt this protocol.

I could this this work.

So:

• For "dependencies" we could enforce consistency with the publish script.
• For "dev dependencies" if they are duplicates, hoist them to the root package (unless I'm missing something from [docs-infra] Migrate lodash to es-toolkit base-ui#2801 (comment)). Once hoisted, no need for catalog.
• And for the few cases that get misaligned, rely on Renovate to update them at the same time to eventually match.
• Trend toward removing the catalog, unless the above are not enough.

[Janpot]

Once hoisted, no need for catalog.

or, once linted, no need for hoisting 😬

edit: Just to be clear, I was just being tongue-in-cheek here (sry, couldn't help it), I don't think it matters too much for dev dependencies, either way.