[rush] update `rush-pnpm update` to update the pnpm-config.json catalog data
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- nodejs, typescript
- Domain
- build-system, cli, tooling
Research direction
Trace the rush-pnpm update command and its handling of pnpm-config.json, comparing it with how native pnpm updates catalogs in pnpm-workspaces.yaml and package.json files. Start by locating the command entry point and existing update tests, then verify that catalog changes are written to pnpm-config.json and that the command no longer passes without updating anything.
Written by the indexing model from the issue text.
Description
The native pnpm update updates any catalogs defined in the pnpm-workspaces.yaml file with whatever changes it would have otherwise made to the package.json files.
With catalogs now living in pnpm-config.json for Rush monorepos, it'd be nice to have the rush-pnpm update behaviour update that location instead.
Currently, when you run the command, it passes but nothing is updated.
- Dominant language
- TypeScript
- Stars
- 6.5k
- Forks
- 708
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 62
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/rushstack
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in microsoft/rushstack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
bcgov/bc-wallet-mobile#4761 · 1 comment ·
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100