Hello all. I have a pretty straightforward stack with 30 different lambda endpoints and I find it's getting slower and slower to do live development using the vscode debugger. Let's say I make a change in one of the lambda functions (change doesn't impact other lambdas) I often have to wait a full minute before the lambda code is actually available for execution (any attempts I make before that typically times out on the caller side since the lambda doesn't respond before timing out). The "Functions: Done building" is almost instantaneous. The lambda eventually gets run but roughly 60 seconds after I saved my code change.
So I'm just wondering if this common to most of us or am I an exception ?
Also there is no visual indication that the code is actually live and ready.
IMPORTANT: I know this is a problem specific to using vscode debugger because if I just do the SST start from a terminal the changes are available almost instantaneously. So something might be wrong in my vscode setup...
t
thdxr
05/12/2022, 5:23 PM
the vscode debugger has a memory leak that is exacerbated by the way we spawn node procs for each function
the good news is we know how to fix it and we're planning to work on it sometime after our conference
thdxr
05/12/2022, 5:24 PM
I'd suggest maybe not using the vscode debugger until we fix it and using poor man console.log debugging
e
Erik Robertson
05/12/2022, 5:31 PM
Thanks for that super quick feedback. Yeah I'd definitely be a faster coder by dropping back to console.log debugging but I really like the debugger capabilities so I'm torn 😄 But I'll probably follow your advice for now. Just to make sure I do things right though : do you confirm that the only way for now use the vscode debugger is by launching the npm run start from within vscode ? There is no way to run the stack outside the console and attach the debugger to it ?
t
thdxr
05/12/2022, 5:32 PM
I think there is but as soon as you attach the debugger you'll likely start to see the same memory issues
r
Ross Coundon
05/12/2022, 5:33 PM
Or use WebStorm 😉
e
Erik Robertson
05/12/2022, 5:36 PM
@thdxr ok, thanks I'll see if I can figure out how to attach and see if it makes any difference.
@Ross Coundon you're right that I haven't considered other options. I've never tried webstorm... Yet 😉
r
Ross Coundon
05/12/2022, 5:56 PM
I've found Webstorm to be generally more performant and more powerful in terms of it being a fully fledged IDE