3 ms·
One (sort of accidental I assume) selling point of Svelte that wasn't mentioned here is that the stack trace is legible. Working with this framework I found th
by Tade0 4y ago
One (sort of accidental I assume) selling point of Svelte that wasn't mentioned here is that the stack trace is legible.
Working with this framework I found that it was very easy for me to trace back to where the change that caused the error happened.
You don't get this in most frameworks, which hide everything under layers of event handlers, schedulers and whatnot.
- Sammi 4y agoThis should really be an explicit goal of a frontend framework and a pain point I have encountered often in React and Angular. How are you supposed to debug stuff if the stack trace isn't even legible?
- solardev 4y agoDoes using a debugger help? (like in VScode or IntelliJ). The React stack trace is so useless I find myself just stepping through the code and setting breakpoints when I need to actually locate the source of an issue. Is there a better way, in React or other languages?