feat(v4-to-v5): upgrade to new codemod
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Current state
Theses codemod as considered as legacy because they was using codemod v0
Also there aren't maintained anymore.
What we have todo
- migrate them to ast-grep instead of jscoshift
- publish them
Contributor guide
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 in the linked codemods/webpack/v5 directory and inspect the existing codemods and their current jscoshift-based setup. Migrate the codemods to ast-grep, then follow the repository's publishing process; done means the migrated codemods are published.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100