What's the best way to debug a

sst.Script

? Should I temporarily convert it to a

sst.Function

and then call it manually?

I imagine you could define your handler as the source for the

sst.Script

function handler as well as a vanilla

sst.Funtion

that you could more easily invoke. but sst.Script is a lambda function underneath isn’t it? should be able to find and invoke that separately from any CDK hook/stack.

Thanks @Blake E

Thanks. Converting it to a function worked. I think that might be the best way anyway, it can be debugged locally and doesn't prevent the stack deploying if there is an error.