catalog on codemod.com does not seem to be updated to the latest build
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
When I ran the codemod on my project, it migrated all dependencies to the catalog, but it looks like this behavior was fixed in #6. codemod.com says this package is legacy and was last published 2+ years ago, but the code in the codebase is much newer than that.
I pulled the code and ran the workflow locally after a build, and it seemed to do the right thing. So it seems the package getting pulled from codemod.com does not have the updated code.
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
Compare the package served from the codemod.com catalog registry with the current repository build, using issue #6 and the local workflow run as references. Trace the build and publishing workflow to find where the stale package is produced or selected. Done means codemod.com serves the current build and no longer applies the behavior fixed in #6.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100