swc-project / swc-project/pkgs
@swc/cli execute timing regression/slowdown
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 86
- Forks
- 44
- Avg merge
- 3d 49m
- Merged PRs (30d)
- 1
Description
Description
I saw a huge performance regression while we update @swc/cli from 0.1.62 to 0.3.10.
Timings
0.3.10 (latest)
https://github.com/bobaaaaa/swc-cli-bug/actions/runs/8355308408/job/22870145794
Successfully compiled: 2 files with swc (85.49ms)
0.1.65 (last version of 0.1.x)
https://github.com/bobaaaaa/swc-cli-bug/actions/runs/8355345456/job/22870250651
Successfully compiled: 2 files with swc (13.6ms)
How to reproduce
I created a small project with both versions + CI + more infos:
https://github.com/bobaaaaa/swc-cli-bug
❤️
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
Start with the linked swc-cli-bug reproduction project and compare the GitHub Actions runs for @swc/cli 0.3.10 and 0.1.65. Reproduce the reported timings for compiling two files, then identify where the slowdown was introduced; done means the regression is explained and the newer version no longer shows the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100