Chrome 131 will not load page when break points present

[michaeldobeson]

Describe the bug

I have a legacy vite project but also have replicated with clean vite project.

% npm create vite@latest
Need to install the following packages:
create-vite@5.5.5
Ok to proceed? (y) y

npx
create-vite

✔ Project name: … vite-project
✔ Select a framework: › React
✔ Select a variant: › TypeScript

Scaffolding project in /Users/michaeldobeson/Temp/ViteTest/vite-project...

Done. Now run:

cd vite-project
npm install
npm run dev

Launching a debug session in vscode with chrome shows the page as expected. Creating any break point and reloading the debug session hangs the page. It appears to hang on the line

const hmrConfigName = "vite.config.ts";

In my legacy project it would hang on the line
const hmrConfigName = HMR_CONFIG_NAME

This works fine in Chrome 130
Firefox is unaffected.

Can also replicate in current build of Edge.
Replicated on multiple macOS Machines on Sonoma, Sequoia, BigSur

Reproduction

na

Steps to reproduce

% npm create vite@latest
Need to install the following packages:
create-vite@5.5.5
Ok to proceed? (y) y

npx
create-vite

✔ Project name: … vite-project
✔ Select a framework: › React
✔ Select a variant: › TypeScript

Scaffolding project in /Users/michaeldobeson/Temp/ViteTest/vite-project...

Done. Now run:

cd vite-project
npm install
npm run dev

System Info

Replicated on multiple macOS Machines on Sonoma, Sequoia, BigSur
Chrome 131

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.

[bluwy]

If this only happens in Chrome 131 and other chromium-based browsers, wouldn't that be a Chrome bug? Should it be reported there instead?

[michaeldobeson]

I understand that is certainly a possibility. Is this not a concern for the vite community? Chrome/Vscode/MacOS is hardly an obscure setup. I could not see others reporting this issue and thought it might be worth while raising the issue and reporting what I found so others don't waste the time I did trouble shooting.

[bluwy]

For sure, but if the issue lies in Chrome 131 and it's not reported there, the issue will never get fixed and this will keep staying open. I'm fine with leaving this open so users can find a single discussion about this, but since it's looks like there's nothing Vite can do to fix this (the breakpoint hanging seems arbitrary to me), we need to move the needle elsewhere.

[Chenyichen12]

Same issue in windows. Now I can only use console.log to debug. too bad

[hi-ogawa]

Not sure if it's same but there was vscode issue recently #18555, microsoft/vscode#232651 Can you check you're on the version they suggest?

[Chenyichen12]

microsoft/vscode#232651，
ok, when I use the extension of js debug nightly. The problem solved soon. This seems to be a problem with vscode. thanks