Jest coverage with @swc/jest reports imports (and other differences)

[SimonMueller]

Describe the bug

After switching from babel-jest to @swc/jest as jest transformer and after running the coverage again i saw some really different and higher numbers of coverage with @swc/jest.

I investigated for a bit and found the main cause to be that the module imports are reported as relevant and therefore covered lines aswell. This changes the coverage percentage of a bigger project drastically as shown in the reproduction linked.

Is this behaviour intended or did i miss something in the configs?

Thx in advance.

Input code

See reproduction repo.

Config

See reproduction repo.

Playground link (or link to the minimal reproduction)

https://github.com/SimonMueller/swc-jest-coverage-repro

SWC Info output

Operating System:
    Platform: linux
    Arch: x64
    Machine Type: x86_64
    Version: #1 SMP Fri Mar 29 23:14:13 UTC 2024
    CPU: (16 cores)
        Models: Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz

Binaries:
    Node: 20.11.0
    npm: 10.2.4
    Yarn: 1.22.15
    pnpm: N/A

Relevant Packages:
    @swc/core: 1.7.18
    @swc/helpers: N/A
    @swc/types: 0.1.12
    typescript: 5.1.6

SWC Config:
    output: N/A
    .swcrc path: N/A

Next.js info:
    output: N/A

Expected behavior

Same coverage report as with "babel-jest" transformer.

Actual behavior

Imports are reported as relevant lines and coverage report has other differences too which results in a much higher coverage than with "babel-jest".

Version

1.7.18

Additional context

No response