Ari Perkkiö

> I'm thinking we could use a path like `../prev-lesson-folder` Where would this path be used? In `.tk-config.json` that is put in lesson's `_files` or `_solution`? > ### Describe the...

Has this ever worked correctly? I just tested `2.0.2`, `1.2.2`, `1.0.0` and `0.33.0`. The error is shown incorrectly on all those versions.

It's expected that this file is instrumented when you disable all `coverage.excludes` and use the default `coverage.includes: ['**']`. The reason why this errors comes up is that `vitest:mocks` plugin has...

I guess this is the specification for Cobertura? https://github.com/cobertura/web/blob/master/htdocs/xml/coverage-04.dtd Looks like Istanbul reporters don't add `` at all: https://github.com/istanbuljs/istanbuljs/blob/main/packages/istanbul-reports/lib/cobertura/index.js#L79-L137 I would recommend to open an issue at: https://github.com/istanbuljs/istanbuljs/issues

Closing as upstream issue. There's nothing to change on Vitest side. Note that you can also create custom reporters: https://vitest.dev/guide/coverage.html#custom-coverage-reporter.

I've used `exclude: ['src/content']` to avoid these errors. I'm not sure if it's even possible to fix this properly for typescript. https://github.com/AriPerkkio/tutorial-vite-plugin/blob/1f161a22bd80c9529ceeac8080dfb27f3db8a318/tsconfig.json#L12

I guess this doesn't show up in our own tests or ecosystem ci due to locally linked packages. It would be great to be able to replicate this issue in...

I think errors have always been there. @Nemikolh any ideas where they come from? > and it doesn't build It does build successfully. In the end of your log output...

> just thinking of it as a newbie - red error notices are scary I agree! We should get rid of these errors. The `build` command seems to run `astro...

There's a lot of similar reports on Astro about this too. We should go through their reports and look for solutions there 🤔 - https://github.com/withastro/astro/issues/11390 - https://github.com/withastro/astro/issues/6631