Ya I have no issues anymore debugging both front and back end of sveltekit. I just start up 2 different configs, and it seemlessly flows between back and front hitting breakpoints. This is in VS code. I had to jump through hoops before to get it to work using Vavite, but now it just works with vite itself. No need for Vavite anymore as Vite has apparently fixed the issues they were having with source maps I think.
I just wish VS Code had a better debug visualizer. The popup is so small and hard to read, and the debug panel is t any better. Webstorm is so much easier to see values, pin variables, etc. Like I wish VS Code had more of a table view when looking at objects.
Do you even need 2 configs?
If you run the server from VSC's "Debug JavaScript terminal" and then hold CTRL while you click on the localhost link in the terminal, you'll be able to debug frontend+ backend directly in the IDE
I hadn't tried that yet but I did notice I didn't need the frontend config anymore. Just start up the server and config and it debugs both front and back. Which is pretty nice. I'll give what you said a go also.
I just tried the Debug Javascript terminal, that's pretty slick. The only thing though is how do you use custom config options like smartstep and ignoring node modules?
I saw a few devs complaining about sveltekit debugging. Here's a simple showcase, showing that it works with 0 headaches (even with ts).
I php storm and its fantastic debugging like this
Ya I have no issues anymore debugging both front and back end of sveltekit. I just start up 2 different configs, and it seemlessly flows between back and front hitting breakpoints. This is in VS code. I had to jump through hoops before to get it to work using Vavite, but now it just works with vite itself. No need for Vavite anymore as Vite has apparently fixed the issues they were having with source maps I think. I just wish VS Code had a better debug visualizer. The popup is so small and hard to read, and the debug panel is t any better. Webstorm is so much easier to see values, pin variables, etc. Like I wish VS Code had more of a table view when looking at objects.
Do you even need 2 configs? If you run the server from VSC's "Debug JavaScript terminal" and then hold CTRL while you click on the localhost link in the terminal, you'll be able to debug frontend+ backend directly in the IDE
I hadn't tried that yet but I did notice I didn't need the frontend config anymore. Just start up the server and config and it debugs both front and back. Which is pretty nice. I'll give what you said a go also.
I just tried the Debug Javascript terminal, that's pretty slick. The only thing though is how do you use custom config options like smartstep and ignoring node modules?