swc-project / swc-project/swc-node
Comparison with ts-node's --swc flag
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 95
- Avg merge
- 14d 11h
- Merged PRs (30d)
- 1
Description
ts-node has supported custom transformers for over a year now, and with that, has included support for doing transformation with swc. In recent versions (released February 2022), it also supports a simple --swc flag which handles setting the transformer up for you.
With that option set, is there a compelling reason to choose this library instead? I've been really happy with my ts-node based workflow, but am wondering if it could be even better.
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
Review the comparison between swc-node and ts-node's --swc flag using the workflow described in the issue. The work is done when the project can clearly state whether swc-node provides a compelling distinction or identify a concrete improvement to pursue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100