nodejs / nodejs/userland-migrations
feat(`correct-ts-specifiers`): migrate to `@next` codemod approche
Open
Nobody has claimed this yet.
let's do it
- Dominant language
- TypeScript
- Stars
- 85
- Forks
- 55
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 9
Description
We need to migrate it to new CLI.
IDK if it's will work because it's use complex node API
https://github.com/nodejs/userland-migrations/tree/main/recipes/correct-ts-specifiers
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 with the correct-ts-specifiers recipe linked in the issue and identify its current implementation and CLI entry point. Compare that implementation with the new CLI migration approach, then verify that the recipe still works with its complex Node API after migration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100