Goal

When using pnpm catalogs, the pnpm update command should work. Today it ignores any dependencies defined in pnpm-workspace.yaml.

Challenges

• The pnpm update command currently works on a singular package.json at a time. There's likely a refactor needed for pnpm update commands running on separate package.json files to coordinate upgrades of the same dependency across multiple workspace packages.
• The YAML serialization/deserialization library in pnpm does not preserve comments. It's not currently possible to change specifiers in pnpm-workspace.yaml without destroying comments.
  • Some work in progress to switch from js-yaml to yaml: feat(deps): migrate js-yaml to yaml #8326