In Vite version 6, breakpoints do not trigger correctly during build debugging.

[newacorn]

Describe the bug

When upgrading from Vite 5 to Vite 6, the debug configuration file does not work as expected. It has always worked fine in Vite 5. This issue has been tested on both Visual Studio Code and JetBrains platforms, and while the problems manifest differently, neither works as expected.
The current debug screenshots are as follows (including JetBrains and Code):


The debug screenshots after simply changing the dependency version to Vite 5 are as follows:

I'm not entirely sure if this is an issue with Vite. I've searched extensively but haven't been able to resolve it. I would greatly appreciate any hints or guidance here.

Reproduction

https://stackblitz.com/edit/bolt-vue-rzarxbse

Steps to reproduce

Use this simple package.json file, run npm install, and then debug the build script on the corresponding platform.

{
  "name": "vite-vue-typescript-starter",
  "private": true,
  "version": "0.0.0",
  "type": "module",
  "scripts": {
    "dev": "vite",
    "build": "vue-tsc -b && vite build",
    "preview": "vite preview"
  },
  "dependencies": {
    "vue": "^3.5.10"
  },
  "devDependencies": {
    "@vitejs/plugin-vue": "^5.2.1",
    "typescript": "^5.5.3",
    "vite": "^6.0.0",
    "vue-tsc": "^2.2.0"
  }
}

System Info

Need to install the following packages:
envinfo@7.14.0
Ok to proceed? (y) y


  System:
    OS: macOS 14.3
    CPU: (32) x64 13th Gen Intel(R) Core(TM) i9-13900KS
    Memory: 125.88 MB / 64.00 GB
    Shell: 5.9 - /usr/local/bin/zsh
  Binaries:
    Node: 23.5.0 - /usr/local/bin/node
    npm: 10.9.2 - /usr/local/bin/npm
  Browsers:
    Safari: 17.3
    Safari Technology Preview: 18.0
  npmPackages:
    @vitejs/plugin-vue: ^5.2.1 => 5.2.1 
    vite: ^6.0.0 => 6.0.6

Used Package Manager

npm

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]

I suspect this is because IDE ignores node_modules by default. After adding a following .vscode/settings.json, vscode debugger seems to pick up source map properly.

{
  "debug.javascript.terminalOptions": {
    "resolveSourceMapLocations": [
      "${workspaceFolder}/**",
      "!**/node_modules/**",
      "**/node_modules/.vite-temp/**"
    ]
  }
}

Some references

• https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_source-map-resolution
• https://stackoverflow.com/questions/47021083/vscode-debug-code-in-node-modules-directory

[newacorn]

I suspect this is because IDE ignores node_modules by default. After adding a following .vscode/settings.json, vscode debugger seems to pick up source map properly.

{
  "debug.javascript.terminalOptions": {
    "resolveSourceMapLocations": [
      "${workspaceFolder}/**",
      "!**/node_modules/**",
      "**/node_modules/.vite-temp/**"
    ]
  }
}

Some references

• https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_source-map-resolution
• https://stackoverflow.com/questions/47021083/vscode-debug-code-in-node-modules-directory

Thank you very much! It works now.