Hi <@U01JVDKASAC>, I just tried updating to 0.35.2...
# sstp
Phil Astle
07/28/2021, 4:12 PMHi @Frank, I just tried updating to 0.35.2 and got to a point where it failed to start up the live lambda dev session. I switched back to 0.35.1 and it still failed but reported (correctly as it turns out) that it couldn't resolve the location of the handlers for my sst.Api routes. I switched back to 0.35.2 and there were no errors listed - looks like they don't appear now?
So in 0.35.1 I get this but nothing equivalent in 0.35.2 that I could see:
f
Frank
07/28/2021, 4:27 PM
Hey @Phil Astle, just to clarify, you mean if you specify an Api route with a path that doesn’t exist, 0.35.1 shows you the error in the screenshot above, but 0.35.2 doesn’t show you any error?
p
Phil Astle
07/28/2021, 4:27 PMYes, that's right
Phil Astle
07/28/2021, 4:27 PMI'd moved a couple of folders and updated the paths incorrectly.
f
Frank
07/28/2021, 4:28 PM
Oh i see. Let me give it a quick try.
Frank
07/28/2021, 4:49 PM
In 0.35.2, I got this error. Does say what the issue is. Is that what you saw?
p
Phil Astle
07/28/2021, 4:51 PMFor me, it just stopped after reporting this:
Phil Astle
07/28/2021, 4:51 PM(the no package.json bit it always mentions but it never stops it working)
f
Frank
07/28/2021, 4:55 PM
I see. Does it quits after that last line? Or does it hang at
Waiting for the debugger to disconnect…p
Phil Astle
07/28/2021, 5:04 PMquits immediate with no pause
f
Frank
07/28/2021, 9:07 PM
Just submitted a PR to print out descriptive error message when handler can’t be resolved - https://github.com/serverless-stack/serverless-stack/pull/616
Frank
07/28/2021, 9:07 PM
Will go into tonite’s release!
Frank
07/29/2021, 7:53 AM
Fixed in v0.36.0!
p
Phil Astle
07/29/2021, 8:31 AMI only mentioned it because it used to to do it in the previous version, though it definitely will help with debugging those kinds of errors! Quick work as always, thanks 🙂