Source maps in VSCode not working for debug vite.config.ts

[thy486]

Describe the bug

Debug vite.config.ts failed.

Because temporary file ${workspaceFolder}/vite.config.ts.timestamp-xxx.mjs now is move to ${workspaceFolder}/node_modules/.vite-temp/vite.config.ts.timestamp-xxx.mjs

Relevant

#17894

nodejs/node#45196

Impact

Expect FunctionLocation in debugger: ${workspaceFolder}/vite.config.ts

Actual FunctionLocation in debugger: ${workspaceFolder}/node_modules/.vite-temp/vite.config.ts.timestamp-xxx.mjs

Suggestion

Make temporary filepath for 'vite.config.ts' configurable or add document to explain how to debug

Reproduction

https://stackblitz.com/edit/vitejs-vite-w1tz8u4r?file=index.html&terminal=dev

Steps to reproduce

node --inspect ${workspaceFolder}/node_modules/vite/bin/vite
// or run in javascript debugger terminal
npx vite

System Info

System:
    OS: macOS 15.2
    CPU: (10) arm64 Apple M4
    Memory: 133.61 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.12.0 - ~/.local/state/fnm_multishells/67195_1736746164855/bin/node
    npm: 11.0.0 - ~/.local/state/fnm_multishells/67195_1736746164855/bin/npm
    pnpm: 9.14.2 - ~/.local/state/fnm_multishells/31840_1736503379186/bin/pnpm
    bun: 1.1.42 - ~/.bun/bin/bun
  Browsers:
    Chrome: 131.0.6778.265
    Safari: 18.2
  npmPackages:
    vite: ^6.0.6 => 6.0.7

Used Package Manager

pnpm

Logs

No response

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.

[hi-ogawa]

It's likely a duplicate of #19110. Can you try this .vscode/settings.json #19110 (comment)?

[thy486]

它可能与#19110重复。您可以尝试这个.vscode/settings.json #19110 (评论)吗？

Got it! I will close it. But I still hope the above suggestions can be optimized.

[hi-ogawa]

I was thinking that running debugger on vite.config.ts is not so common, but maybe I'm wrong. If users often get caught by this, we can mention the workaround on documentation.

[thy486]

I was thinking that running debugger on vite.config.ts is not so common, but maybe I'm wrong. If users often get caught by this, we can mention the workaround on documentation.

When developing the vite plugin, it seems that the plugin code (in the project) cannot be mapped back(
setting.json has been set correctly according to the above suggestion and vite.config.ts has been successfully mapped). But revert this commit(#18833 ) can be mapped back, but the mapped file path is ${workspaceFolder}/node_modules/.vite-temp/src/xxx.

If you use the commented code, you can map successfully

Reproduction

https://stackblitz.com/edit/vitejs-vite-uk5hhx86?file=index.mjs

Steps to reproduce

// javascript debugger terminal
node index.mjs

[hi-ogawa]

@thy486 This looks like a slightly different issue and more complicated. Probably vscode got confused with plugin/index.ts's source map coming from vite.config.ts bundling and ssrLoadModule.

I'm not sure how this setup was working on Vite 5. Can you create a new issue for this?

[thy486]

@thy486 This looks like a slightly different issue and more complicated. Probably vscode got confused with plugin/index.ts's source map coming from vite.config.ts bundling and ssrLoadModule.

I'm not sure how this setup was working on Vite 5. Can you create a new issue for this?

I seem to know why, it should be the sourcemap of these two modules
points to the same file.

I think this is just a phenomenon, haha