svelte 5 $runes debugging

[weepy]

I don't know if there's a way to improve this, but as a Svelte user, I'm finding that stepping through Svelte 5 is painful compared to Svelte 4.

I have a moderately complex project and I rely on Chrome Devtools to step through the javascript to debug. With Svelte 5, we end up stepping into compile time code whenever we come across some $state. This means we need to add extra breakpoints and run to hits them in our target code.

As I said I don't know how you might "fix" this since the event state is now runtime rather than compile time, but just sharing here ... and remember sharing is caring ^_^ .

Jonah

[brunnerh]

In the Chrome dev tools, scripts can be put onto an ignore list so the debugger does not stop there.
If a chunk for the Svelte internals is generated, you might be able to use this feature on that.

[weepy]

OK - added all 3rd party scripts to ignore list - seems good so far! Adding one at a time was less plausible as there were quite a lot

…

On Tue, Nov 11, 2025 at 9:24 AM brunnerh ***@***.***> wrote: In the Chrome dev tools, scripts can be put onto an ignore list so the debugger does not stop there. If a chunk for the Svelte internals is generated, you might be able to use this feature on that. — Reply to this email directly, view it on GitHub <#17136 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAGNBWH5UZ25VHISSC73D34GMKRAVCNFSM6AAAAACLX3QJ22VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOJTGQYTINA> . You are receiving this because you authored the thread.Message ID: ***@***.***>