fix(coverage): vite-node to pass correct execution wrapper offset

[AriPerkkio]

Description

• Fixes Incorrect coverage in web workers with @vitest/web-worker and @vitest/coverage-v8 #7379
• Proper fix for TypeError: Cannot read properties of undefined (reading 'endCol') #6297

Makes vite-node to hold info about the execution wrapper it uses when executing modules. Coverage providers are passed this info on the test runner thread so that they can attach it into the coverage results. There's no longer need to hard-code the wrapper length on main thread codebase. The example web-worker.test.ts has a case where in a single test runner thread some code is executed with 185 long wrapper and some with ~430 long wrapper.

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 vitest-dev ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	89102c3
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/67ac6c5dc5f70e000834fac7
😎 Deploy Preview	https://deploy-preview-7417--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[hi-ogawa]

Makes sense to me 👍
I'm wondering what happens if the same file is imported from test and from @vitest/web-worker. Does startOffset conflict (last loaded win?) and so coverage is likely broken?

[AriPerkkio]

Makes sense to me 👍 I'm wondering what happens if the same file is imported from test and from @vitest/web-worker. Does startOffset conflict (last loaded win?) and so coverage is likely broken?

Yep, coverage could break then. Also V8 gets confused as the same file ID had different contents when executed. The script coverage is a mess then.

[sheremet-va]

Do we need to update vitest's package.json's peerDependencies? Is it technically a breaking change?

[AriPerkkio]

Do we need to update vitest's package.json's peerDependencies? Is it technically a breaking change?

Which package here?

vitest/packages/vitest/package.json

Lines 124 to 132 in 12eaf3e

	"peerDependencies": {
	"@edge-runtime/vm": "*",
	"@types/debug": "^4.1.12",
	"@types/node": "^18.0.0 || ^20.0.0 || >=22.0.0",
	"@vitest/browser": "workspace:*",
	"@vitest/ui": "workspace:*",
	"happy-dom": "*",
	"jsdom": "*"
	},

Or you mean about using mixed versions? A year ago (#5208) we made the decision that Vitest monorepo's packages do not work with mixed versions. All packages must have the same version. And we've been introducing breaking changes between the packages ever since. There are also runtime warnings in @vitest/browser, @vitest/ui and coverage packages about mixed versions.