chore: test oxc module runner transform

[hi-ogawa]

Description

Base branch #7509
Diff sheremet-va/vitest@feat/rolldown-support...hi-ogawa:vitest:chore-oxc-module-runner-transform

Testing rolldown-vite from vitejs/rolldown-vite#85

notes

• default export/import value identity module runner transform doesn't preserve default export value identify oxc-project/oxc#9645
• error stack call column
  • this probably doesn't matter and technically new one is the right one matching nodejs Vite module runner call stack column is slightly different from Node vitejs/vite#19625

someFn()
      ^  [before]
^ [after]

• Plain js is transformed by oxc, so comments are all stripped. This was already the case for ts files due to esbuild, so it's not likely this change significantly affects users.

• something wrong with pnpm -C test/cli test /git-changed and test/cli/fixtures/git-changed/related fix(transformer/module_runner): handle re-export as deps oxc-project/oxc#9696

vitest/test/cli/fixtures/git-changed/related/src/sourceC.ts

Lines 1 to 2 in b14753a

	// re-exporting for deep changed detection
	export { A } from './sourceA'

• v8 coverage
  • test/coverage-test/fixtures/src/load-outside-vite.cjs
    • oxc transform appending ; somehow increases branches count. This is likely not essential and it just got manifested due to plain js being transformed (see 3rd note above).
  • test/coverage-test/test/pre-transpiled-source.test.ts
    • no change in functions/branches count, so this is probably fine.
  • web worker
    • minor single line coverage difference likely due to both Vite and Vitest messing with new Worker(new URL(..), { type: "module" }) and OXC finally adding new lines somewhere. this is probably fine and also the bug might be elsewhere.
  • vue
    • coverage already fluctuates between providers, so this is probably fine.

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	b14753a
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/67d0f99cd8cc32000884c14c
😎 Deploy Preview	https://deploy-preview-7646--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.