feat(jest): SWC support for jest

[glorat]

What kind of change does this PR introduce? (check at least one)

• [ ] Bugfix
• [ ] New test runner
• [ ] Documentation
• [X] Feature
• [ ] Code style update
• [ ] Refactor
• [ ] Build-related changes
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

• [ ] Yes
• [X] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• [X] It's submitted to the dev branch and not the master branch
• [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• [ ] It's been tested on Windows
• [ ] It's been tested on Linux
• [X] It's been tested on MacOS
• [X] Any necessary documentation has been added or updated in the docs (for faster update click on "Suggest an edit on GitHub" at bottom of page) or explained in the PR's description.

If adding a new feature, the PR's description includes:

• [X] A convincing reason for adding this feature - see issue #307

Other information:

[glorat]

Some testing on a couple of projects I run. To test performance, I am using npx jest --no-cache and running a few times to get a median result.

On the smaller project on a fast machine

• ts-jest - 5.6 seconds
• swc/jest - 2.1 seconds

On a large project including component testing on a slow machine

• test-jest - 47 seconds
• swc/jest - 17 seconds

On same project without any component testing on a slow machine

• ts-jest - 12 seconds
• swc/jest - 9 seconds

[IlCallo]

Hey there! I see this is still hanging here in draft mode, are you still interested in contributing?

[glorat]

Hey there! I see this is still hanging here in draft mode, are you still interested in contributing?

Sorry for radio silence... what's happened is that my projects have switched to vite and vitest so this is left hanging. For anyone still on webpack framework wanting to use SWC, this change is still good. But I don't think it is worth the effort anymore to make this a real plug-in enhancement. Instead, might simply be better to leave documentation on how people could switch to SWC.

[IlCallo]

Ok, no problem, I'll close the PR in that case Thanks for clarifying!