Open rikisamurai opened 1 year ago
But if i switch to ts-jest, it works well
const config: JestConfig = {
// ...
transform: {
'^.+\\.(ts|tsx)?$': 'ts-jest',
'^.+\\.(js|jsx)$': 'babel-jest',
// '^.+\\.(t|j)sx?$': ['@swc/jest', swcConfig as Record<string, unknown>],
},
// ...
};
I've also noticed this issue, it seems to affect export statements that aren't imported elsewhere in our codebase. Also seems to be a similar issue as #119.
Obviously in some cases a solution is to remove the export, but ideally we'd be able to ignore it.
Here's a screenshot of an example from the lcov output:
Even moving the comment to a different spot doesn't resolve it:
The only way I'm able to resolve it is by removing the export:
Or by / istanbul ignore file / but that's not ideal.
Happy to try and reproduce with a repo if needed
I'm the author of #119 and I guess export may be the reason it is not ignored. We are using nextjs so components have to be default exported to be picked up
I have added / istanbul ignore next / , but it doesn't work. here is my project: https://github.com/rikisamurai/swc-jest-issue. You can reproduce the issue by running the command
pnpm test
version:swc/jest doesn't ignore
export const countAtom = atom(0);
source code
jest config: