Inspecting import values in debuggers returns Uncaught ReferenceError: importName is not defined

Describe the bug

I am trying to use the debugger while running vitest specs. Breakpoints work, and debugging of variables defined inside the file work as well.

test repro: https://github.com/DamianPereira/vitest-debugger-repro

You can see that the source map failed to account for the imports, and shows them as __vite_ssr_import_0__

This also happens with webstorm js debugger.

Reproduction

Clone the repo, and run

yarn vitest --inspect-brk ----no-file-parallelism

Then open chrome://inspect in any chrome based browser. And inspect the file. Add a breakpoint where it shows in the screenshot, and try debugging the value.

The repo contains a brand new npm create vite@latest + yarn add -D vitest with nothing else.

System Info

System:
    OS: macOS 15.6.1
    CPU: (14) arm64 Apple M4 Max
    Memory: 2.19 GB / 36.00 GB
    Shell: 4.2.1 - /opt/homebrew/bin/fish
  Binaries:
    Node: 20.19.4 - /Users/damian/.local/share/mise/installs/node/20.19.4/bin/node
    Yarn: 1.22.22 - /Users/damian/.local/share/mise/installs/node/20.19.4/bin/yarn
    npm: 10.8.2 - /Users/damian/.local/share/mise/installs/node/20.19.4/bin/npm
    pnpm: 10.12.4 - /Users/damian/.local/share/mise/installs/node/20.19.4/bin/pnpm
  Browsers:
    Chrome: 142.0.7444.176
    Firefox: 145.0.2
    Firefox Developer Edition: 146.0
    Safari: 18.6
  npmPackages:
    vite: ^7.2.4 => 7.2.6
    vitest: ^4.0.15 => 4.0.15

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.

Clone the linked vitest-debugger-repro repository and run yarn vitest --inspect-brk ----no-file-parallelism. Inspect the generated debugger source map around imported values and compare the displayed __vite_ssr_import_0__ names with the original imports. Done means imported values can be inspected without an importName ReferenceError in Chrome DevTools and the WebStorm JavaScript debugger.