okay, I see that sst.Function makes sense, but wouldn’t it be possible to just add the debug stack to my existing cdk app? I don’t want to change every stack for SST

Hey @p0wl, currently you can’t pull out the debug stack and use it with a native CDK app.

I would love to install it as an add-on (e.g. adding it as a separate stack instead of changing cdk.App to sts.App) and maybe provide a list of lambda functions to that stack. The idea behind sst is genius, but it feels like a big requirement to try it if it its necessary to sst.Function , sst.App and sst.Stack (as said we cannot use esbuild currently).

Oh I see.. yeah the

sst start

actually starts a watcher that rebuilds all the function code on save. And that process has deep tie-in into

sst.Function

and esbuild.

yeah, I totally agree that this is a very nice workflow and I will use that for new projects, but it is hard to buy into sst with existing projects.

yeah i hear you.. that’s totally fair

I’d love a “mini version”, where you just add the debug stack, maybe install a nodejs dependency (or a layer or whatever) in some lambdas that you know you want to use with sst.

yeah that makes sense

Should I put that somewhere? In a github issue or so?

For sure.. you can open a discussion here https://github.com/serverless-stack/serverless-stack/discussions