The choice to use esbuild everywhere was consistent, but being locked out of aspects of typescript that we would get in normal CDK (i’m thinking the cdk.json (“app”: “npx ts-node --prefer-ts-exts bin/demo-ts.ts”,) can cause some headaches if I’m not expecting it. I’d almost prefer that normal cdk is used for everything except the start command (which really only needs to watch the lambda functions right?) The lambas could be build as normal for the deployment scenario and the start script would do its thing about swapping in the jump function and discovering functions to build and watch locally. Still new to the code so I’m figuring out what goes where and why, please don’t take it as criticism of an amazingly useful kit!

As for now, as you suggested, let’s add an

esbuildConfig

param to the

sst.json

. I’m also thinking to make all functions respect this flag by default.