Describe the bug

some files of my lib are named of chinese words，so tsc generates sourcemaps

like this，but vite's dev mode seems not work properly with this sourcemap.
will output logs ‘failed to load sourcemap’

Reproduction

it's hard to provide

System Info

System:
    OS: Windows 10 10.0.19044
    CPU: (16) x64 Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz  
    Memory: 9.66 GB / 31.82 GB
  Binaries:
    Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.1.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 105.0.5195.127
    Edge: Spartan (44.19041.1266.0), Chromium (105.0.1343.33)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @vitejs/plugin-legacy: ^1.8.2 => 1.8.2 
    @vitejs/plugin-vue: ^2.0.0 => 2.3.3 
    @vitejs/plugin-vue-jsx: ^1.3.1 => 1.3.10 
    vite: 2.9.13 => 2.9.13

Used Package Manager

pnpm

Logs

下午6:41:32 [vite] Failed to load source map for /@fs/C:/projects/draw-board/packages/graph-model/dist/common/图元/时钟集/秒针.js.
下午6:41:32 [vite] Failed to load source map for /@fs/C:/projects/draw-board/packages/graph-model/dist/common/图元/时钟集/时钟中心点.js.
下午6:41:32 [vite] Failed to load source map for /@fs/C:/projects/draw-board/packages/graph-model/dist/common/图元/时钟集/角名.js.
下午6:41:32 [vite] Failed to load source map for /@fs/C:/projects/draw-board/packages/graph-model/dist/common/图元/时钟集/刻度.js.
下午6:41:32 [vite] Failed to load source map for /@fs/C:/projects/draw-board/packages/graph-model/dist/common/图元/时钟集/内轨迹.js.
下午6:41:32 [vite] Failed to load source map for /@fs/C:/projects/draw-board/packages/graph-model/dist/common/图元/时钟集/外轨迹.js.
下午6:41:32 [vite] Failed to load source map for /@fs/C:/projects/draw-board/packages/graph-model/dist/assets/刻度素材.js

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.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• 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.