Ari Perkkiö

Fixed by https://github.com/stackblitz/tutorialkit/pull/440.

Recently I used this kind of approach to print logged `console.error()` calls only when tests fail. You could extend this logic to capture `.log()` calls as well: https://github.com/AriPerkkio/vitest/blob/f11b6d8a1a688e7bd2ce271969b07ba4c982056f/test/config/test/failures.test.ts#L16-L28

This is also an issue with code coverage packages. As we (intentionally) require all Vitest packages to be on same version, it's not guaranteed that `[email protected]` and `@vitest/@1.5.0` work together....

> why lint is failing on spacing issues on a bunch of files I didn't touch The lockfile contains plenty of changes, including updating `@antfu/eslint-config` which is likely causing the...

This is same as https://github.com/bcoe/c8/issues/172, also mentioned in the description of https://github.com/vitest-dev/vitest/pull/4309. Here's reproduction with just Node without Vitest, `c8` or any other npm package: ```js import { writeFileSync }...

Yup, it does this by AST analysis. Similar how `@vitest/coverage-istanbul` works, but they do that also for V8 coverage. There's still a bug/feature in V8/Node that causes this branch count...

This will be fixed in: - https://github.com/vitest-dev/vitest/pull/7736 

Something is importing the untested `TestNestedUntested`. V8 is reporting coverage for it. Maybe Nuxt imports all those files? ```json { "scriptId": "745", "url": "file:///x/nuxt-starter-gvfsue/components/nested/TestNestedUntested.vue", "functions": [ { "functionName": "", "ranges":...

@FlorianPhilipp2007 could you test if `coverage.provider: 'istanbul'` works better here? Under the hood it works differently than the default `v8` provider. It could help in hiding the untested files, but...

How does Nuxt import those files? Sounds like it's not using the Vite server at all. 🤔 Are there any test runners that can show code coverage of Nuxt projects?