[Bug]: Debug break points breaking svelte 5 application

[vamshinenu]

What happened?

It was happening when I was trying to add debug breakpoints in vscode and here is whats happening..

https://drive.google.com/file/d/1zHVascpkZNbe5D43ICeEeBcsZUORXlIV/view?usp=sharing

thats the video above.

Version

v1.0.326

CLI command to start your dev tool

bun dev

Steps to reproduce (or sample repo)

start a svelte kit project make sure you use, svelte 5, because svelte 4 and below is working...

start the project, and then try adding a debug, point.

Log output

10:38:19.836 info buildHook-85666 file processed (stat): 0 log points, error handler: false, network logging handler: false
10:38:20.611 info host client disconnected: runtimeHook 1001
10:38:20.611 info host client disconnected: runtimeHook
10:38:20.872 info host client connected: runtimeHook { address: '127.0.0.1', family: 'IPv4', port: 51033 }
10:38:22.574 info buildHook-85666 file processed (stat): 4 log points, error handler: false, network logging handler: false
10:38:25.707 info buildHook-85666 file processed (stat): 0 log points, error handler: false, network logging handler: false
10:38:26.151 info host client disconnected: runtimeHook 1001
10:38:26.151 info host client disconnected: runtimeHook
10:38:26.319 info host client connected: runtimeHook { address: '127.0.0.1', family: 'IPv4', port: 51033 }
10:42:31.120 info buildHook-85666 file processed (stat): 0 log points, error handler: false, network logging handler: false
10:42:49.740 info buildHook-85666 file processed (stat): 0 log points, error handler: false, network logging handler: false
10:42:50.297 info buildHook-85666 file processed (stat): 4 log points, error handler: false, network logging handler: false
10:42:55.280 info buildHook-85666 file processed (stat): 0 log points, error handler: false, network logging handler: false
10:42:55.680 info host client disconnected: runtimeHook 1001
10:42:55.680 info host client disconnected: runtimeHook
10:42:55.937 info host client connected: runtimeHook { address: '127.0.0.1', family: 'IPv4', port: 51033 }
10:43:22.278 info buildHook-85666 file processed (stat): 5 log points, error handler: false, network logging handler: false
10:43:23.209 info buildHook-85666 file processed (stat): 0 log points, error handler: false, network logging handler: false
10:43:23.617 info host client disconnected: runtimeHook 1001
10:43:23.617 info host client disconnected: runtimeHook
10:43:23.841 info host client connected: runtimeHook { address: '127.0.0.1', family: 'IPv4', port: 51033 }
10:43:25.582 info buildHook-85666 file processed (stat): 4 log points, error handler: false, network logging handler: false
10:43:26.765 info buildHook-85666 file processed (stat): 0 log points, error handler: false, network logging handler: false
10:43:27.100 info host client disconnected: runtimeHook 1001
10:43:27.100 info host client disconnected: runtimeHook
10:43:27.326 info host client connected: runtimeHook { address: '127.0.0.1', family: 'IPv4', port: 51033 }
10:43:30.664 info buildHook-85666 file processed (stat): 4 log points, error handler: false, network logging handler: false
10:43:31.764 info buildHook-85666 file processed (stat): 0 log points, error handler: false, network logging handler: false
10:43:32.133 info host client disconnected: runtimeHook 1001
10:43:32.133 info host client disconnected: runtimeHook
10:43:32.348 info host client connected: runtimeHook { address: '127.0.0.1', family: 'IPv4', port: 51033 }
10:44:53.632 info host client disconnected: runtimeHook 1001
10:44:53.632 info host client disconnected: runtimeHook
10:44:54.101 info host client connected: runtimeHook { address: '127.0.0.1', family: 'IPv4', port: 51033 }
10:45:06.855 info buildHook-85666 file processed (stat): 4 log points, error handler: false, network logging handler: false
10:45:13.066 info host client disconnected: runtimeHook 1001
10:45:13.067 info host client disconnected: runtimeHook
10:45:23.183 info buildHook-85666 file processed (stat): 0 log points, error handler: false, network logging handler: false
10:45:24.317 info host client connected: runtimeHook { address: '127.0.0.1', family: 'IPv4', port: 51033 }
10:45:31.674 info host client disconnected: runtimeHook 1001
10:45:31.674 info host client disconnected: runtimeHook

[smcenlly]

Thanks for reporting the problem.

This is fixed in the latest version of Console Ninja, v1.0.327.