nodejs / nodejs/userland-migrations
Codemod to help adoption of types stripping
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 85
- Forks
- 55
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 9
Description
Description/Context
To enable TypeScript support on Node.js, Marco implement types stripping. This approach is now supported by the TypeScript transpiler and is on its way to becoming stable on Node.js. That is why we must try to create one or more codemods that will enable adoption of this approach.
Todo
- Use right file extension on import specifier
@nodejs/correct-ts-specifiers(need to be updated to new codemod paradigm)
Thing to define
- How to go away from
enum - What do we have to change in the
tsconfig.json
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 by reviewing the existing @nodejs/correct-ts-specifiers codemod and its migration to the new codemod paradigm. Then examine the open questions around enum usage and tsconfig.json changes; done means defining and implementing codemods that support adoption of TypeScript types stripping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100