`ENAMETOOLONG` error with a long file path when `server.debug.dump` flag is on

Describe the bug

it happens when a test case file has a long path

the error message is like:

 FAIL  App.very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_long.spec.tsx [ App.very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_long.spec.tsx ]
Error: ENAMETOOLONG: name too long, open '/xxx/reproductions/.vite-node/dump/_Volumes_jinjiang-portable-disk_Developer_personal_reproductions_App_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_very_long_spec_tsx--51554923.js'

Original discussion: https://github.com/vitest-dev/vitest/discussions/7662

Reproduction

https://github.com/Jinjiang/reproductions/tree/vitest-dump-20250327

System Info

System:
    OS: macOS 15.4
    CPU: (8) arm64 Apple M1
    Memory: 182.92 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.14.0 - ~/.local/share/mise/installs/node/22/bin/node
    Yarn: 1.22.18 - ~/.yarn/bin/yarn
    npm: 10.9.2 - ~/.local/share/mise/installs/node/22/bin/npm
    pnpm: 10.6.5 - ~/Library/pnpm/pnpm
    bun: 1.1.36 - ~/.local/share/mise/installs/bun/latest/bin/bun
  Browsers:
    Safari: 18.4
  npmPackages:
    @vitejs/plugin-react: ^4.3.4 => 4.3.4 
    vite: ^6.2.3 => 6.2.3 
    vitest: ^3.0.9 => 3.0.9

Used Package Manager

pnpm

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.

Start by running the linked reproduction with the server.debug.dump flag enabled and a test case file with a long path. Trace the dump behavior that produces the reported ENAMETOOLONG error; done means long test paths no longer fail while debug dump output remains available.