You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've recently started using ViteJS instead of webpack. In dev mode, instead of bundling everything up, it serves every file separately and transpiles it on the fly.
But when I set a breakpoint in vscode, refresh the page, the browser (Edge launched via debugger) stops briefly after every file is loaded and then continues to the next file. Considering they aren't bundled, there can be hundreds of files included in the app and the entire process of loading the app lasts over a minute. Then the page refreshes for some reason and the process starts all over. The page is usually never loaded and the breakpoint never hit.
When I open the exact same app via Edge not launched via debugger, this doesn't happen - the page loads up correctly and the breakpoint is hit. This leads me to believe it's an issue in between vscode's debugger and Edge.
The exact same thing happens with Google Chrome. Firefox doesn't have this issue (used the Firefox Debugger Extension).
VS Code version: Code 1.76.2 (ee2b180, 2023-03-14T17:55:54.936Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No
Remote OS version: Linux x64 5.4.0-131-generic
System Info
Item
Value
CPUs
11th Gen Intel(R) Core(TM) i5-1145G7 @ 2.60GHz (8 x 1498)
If I set the breakpoint in browser, not in the vscode, it works as expected. So, this issue seems to happen only when I set the breakpoint in vscode's editor.
This is by design, we use instrumentation pauses to set scripts in sourcemaps prior to evaluation. Unfortunately it's not possible for us to avoid showing the overlay message when the browser devtools are open, since this is registered and controlled by them.
If we do microsoft/vscode-js-debug#1214, it may be possible to configure the debugger precisely enough that script URIs can be known ahead of time and avoid the instrumentation pause in some cases, but an on-the-fly "dev server" kind of scenario isn't one of those since we don't know about the sourcemaps ahead of time.
Type: Performance Issue
I've recently started using ViteJS instead of webpack. In dev mode, instead of bundling everything up, it serves every file separately and transpiles it on the fly.
But when I set a breakpoint in vscode, refresh the page, the browser (Edge launched via debugger) stops briefly after every file is loaded and then continues to the next file. Considering they aren't bundled, there can be hundreds of files included in the app and the entire process of loading the app lasts over a minute. Then the page refreshes for some reason and the process starts all over. The page is usually never loaded and the breakpoint never hit.
When I open the exact same app via Edge not launched via debugger, this doesn't happen - the page loads up correctly and the breakpoint is hit. This leads me to believe it's an issue in between vscode's debugger and Edge.
The exact same thing happens with Google Chrome. Firefox doesn't have this issue (used the Firefox Debugger Extension).
Here's the launch.json config:
VS Code version: Code 1.76.2 (ee2b180, 2023-03-14T17:55:54.936Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No
Remote OS version: Linux x64 5.4.0-131-generic
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Process Info
Workspace Info
Extensions (28)
A/B Experiments
The text was updated successfully, but these errors were encountered: