Inconsistent import.meta.env.SSR (false on vmThreads pool and true on other pools)

[hi-ogawa]

Describe the bug

While making a PR #5561, I just found import.meta.env.SSR works differently on vmThreads.

npm run test
{
  'import.meta.env.PROD': true,
  'import.meta.env.DEV': true,
  'import.meta.env.SSR': true,
  'process.env.PROD': 'false',
  'process.env.DEV': 'true',
  'process.env.SSR': '1'
}

npm run test -- --pool vmThreads --disable-console-intercept
{
  'import.meta.env.PROD': true,
  'import.meta.env.DEV': true,
  'import.meta.env.SSR': false,
  'process.env.PROD': 'false',
  'process.env.DEV': 'true',
  'process.env.SSR': undefined
}

It looks like console is not working on vmThreads, so I needed to use --disable-console-intercept here.

Reproduction

https://github.com/hi-ogawa/reproductions/tree/main/vitest-env

vmThreads doesn't seem to run on Stackblitz

System Info

System:
    OS: Linux 6.8 Arch Linux
    CPU: (12) x64 AMD Ryzen 5 5625U with Radeon Graphics
    Memory: 2.69 GB / 14.98 GB
    Container: Yes
    Shell: 5.2.26 - /bin/bash
  Binaries:
    Node: 20.12.2 - ~/.volta/tools/image/node/20.12.2/bin/node
    Yarn: 1.22.19 - ~/.volta/tools/image/yarn/1.22.19/bin/yarn
    npm: 10.5.0 - ~/.volta/tools/image/node/20.12.2/bin/npm
    pnpm: 8.15.7 - ~/.volta/bin/pnpm
    bun: 1.0.26 - ~/.volta/bin/bun
  Browsers:
    Chromium: 123.0.6312.122
  npmPackages:
    vitest: 1.5.0 => 1.5.0

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.