[Vite -> React -> Typescript + SWC] Empty (no, 0, files found) code coverage report

[sebaguozden]

Describe the bug

Everything runs smoothly with pnpm test-storybook. On the other hand, pnpm test-storybook --coverage returns an empty coverage report.

Steps to reproduce the behavior

1. Run pnpm storybook
2. Run pnpm test-storybook --coverage
3. Console Coverage Summary will be empty (no files found)
4. coverage/storybook/coverage-storybook.json only contains {}

Expected behavior

Show **/*.tsx files on the report.

Screenshots and/or logs

.storybook/main.ts

package.json

EMPTY Coverage (Console) Report

EMPTY Coverage (File) Report

Environment

• OS: Ubuntu 22.04.2 (WSL)
• Node.js version: v20.9.0
• PNPM version: 8.10.2 -> Also happens with NPM version: 10.1.0
• Browser (if applicable): chrome
• Browser version (if applicable): Not Sure (installed through playwright pnpm exec playwright install + pnpm exec playwright install-deps)
• Device (if applicable): Not Applicable

[sebaguozden]

It is related to #17. Addon is not compatible with @vitejs/plugin-react-swc. Any idea how to fix it?

[DawidWraga]

I have the exact same issue but I am not using @vitejs/plugin-react-swc, I have @vitejs/plugin-react in my package.json

[zeroliu]

Checking the coverage-storybook.json output, I find that the missing components are in my output json file but the file path is wrong. Instead of /path/to/my/Component.tsx, they are /path/to/my/Component. I guess that's why the nyc report cannot find them in my cases

[Ravina1604]

I have the exact issue. I am using addon-coverage with @storybook/addon-webpack5-compiler-swc.
My project doesn't work with babel-loader so i removed it from webpack config and custom configured to use swc-loader instead.
and it returns 0 coverage on files

[lcrespom]

I think you are missing a --, try this: pnpm test-storybook -- --coverage.

[bartstcv]

Any update on this one? I also have Vite, React, TS, SWC stack and still suffer from that issue. As Test Addon for Storybook is still in experimental mode, using this coverage-addon is the right way to go. I am even considering switching back from @vitejs/plugin-react-swc to @vitejs/plugin-react, but I woudl rather really avoid that.

[lcrespom]

@bartstcv If you share your scripts from your package.json file, and how you call the code coverage task, I can check if you have the same issue that I had.