VS Code Debugger Stuck in Infinite Loading with Breakpoints Enabled on Vite React JSX Project

[Miderson99]

Description:
I'm experiencing an issue in Visual Studio Code (VS Code) where, upon reloading the debugger or starting it with breakpoints enabled, the browser enters an infinite loading state. This behavior prevents me from proceeding with development and debugging on my Vite React JSX project. Notably, if I disable all breakpoints, the debugger loads and runs as expected.

Steps to Reproduce:

Open a Vite React JSX project in VS Code.
Set breakpoints in the code.
Start debugging or reload the debugger.
Observe that the associated browser enters an infinite loading state when breakpoints are enabled.
Expected Behavior:
The browser should load the application correctly, allowing for debugging with the defined breakpoints.

Observed Behavior:
The browser remains in an infinite loading state with breakpoints enabled. However, when breakpoints are disabled, the debugger functions normally, and the application loads without issues.

Troubleshooting Steps Taken:

Checked the launch.json debug configuration.
Disabled and re-enabled breakpoints.
Updated all debugging-related extensions.
Cleared the browser cache.
Verified for potential port conflicts.
Reinstalled VS Code.
Changed the browser from Edge to Chrome for debugging.
Despite these attempts, the issue persists when breakpoints are enabled.
Additional Information:

VS Code Version: [1.95.1]
Operating System: [Windows 11]
Installed Extensions:
Bookmarks by Alessandro Fragnani
Color Highlight by Sergii N
Color Picker by anseki
Microsoft Edge Tools for VS Code by Microsoft
Prettier - Code Formatter by Prettier
React Native Tools (Preview) by Microsoft
Tailwind CSS IntelliSense by Tailwind Labs

Any assistance in resolving this issue would be greatly appreciated.

[vs-code-engineering]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.95.2. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[fleducKaster]

I've experience the same problem with v1.95.2 Look here: #233432