fix(vitest): json reporter location should include file

[vird]

Description

JSON reporter returns location of error, but there are multiple files. What is origin of line, column? What file?
So I decided to fix that

NOTE. I don't know how to fix test snapshots, so they will run on each machine. File returns absolute path, so matching with snapshot is not possible, I guess

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for fastidious-cascaron-4ded94 canceled.

Name	Link
🔨 Latest commit	4915030
🔍 Latest deploy log	https://app.netlify.com/sites/fastidious-cascaron-4ded94/deploys/65bd62d0e7d0960008eb8b70

[hi-ogawa]

Thanks for the PR. FYI, there were some related discussions in

• fix: match jest json output by providing full stack trace #4843
• fix: match jest json output by reporting location of error in test file #4826

and it looks like including stacktrace in failureMessages is currently considered.

Including location.file also makes sense to me, but could you also check if you might also want stacktrace?

[hi-ogawa]

NOTE. I don't know how to fix test snapshots, so they will run on each machine. File returns absolute path, so matching with snapshot is not possible, I guess

Btw, one way to deal with this type of non-determinism in snapshots is to replace "dirname" with some placeholder value like this:

vitest/test/typescript/test/runner.test.ts

Line 97 in ae73f27

expect(stderr.replace(resolve(__dirname, '..'), '<root>')).toMatchSnapshot()

[sheremet-va]

I don't think having an empty string here is a good idea

[vird]

return file == '' case should be unreachable. Because there should be no error without stack
So it's mostly for convincing typescript that all is ok anyway
If there are line and column, but there is no file, then that's strange input to this function. Strange input - strange output

[sheremet-va]

If you just want to satisfy TS, you can use !

[sheremet-va]

Jest doesn't have a file property. It is inferred from the test name. Vitest reports incorrect location property. This should be fixed by #5434