Moves named catalog deps to unnamed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
make a dep with a named catalog
some package
"graphql": "catalog:graphql15",
with
catalogs:
graphql15:
graphql: ^15.3.0
run pnpx codemod pnpm/catalog
becomes
"graphql": "catalog:",
expected: should leave the named catalog
(Seems like this only reproduces if the named catalog comes after the default one in pnpm-worspace.yaml)
(It's also notable that I had one package referencing graphql not in a catalog and one referencing the named one)
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.
Research direction
Start by reproducing the issue with the shown package dependency, catalogs configuration, and pnpx codemod pnpm/catalog command, paying attention to the named catalog's position in pnpm-worspace.yaml. Trace the codemod entry point for this command and compare packages using the default and named catalogs. Done means the graphql dependency remains catalog:graphql15 after the codemod runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100