Serverless Stack

I don't know what magic SST has to do to functions to necessitate custom bundling steps instead of using CDK's <https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_lambda_nodejs-readme.html|NodejsFunction> but there is some new support for esbuild options like <https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_lambda_nodejs.BundlingOptions.html#inject|inject>...
It would be really terrific IMO if SST was leveraging NodejsFunction (which already supports <https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_lambda_nodejs.BundlingOptions.html|pretty much any esbuild configuration>) so as not to be maintaining a separate similar but less maintained and <https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_lambda_nodejs.NodejsFunction.html|featureful> node bundler

Hey <@U02Q7J6A17S>, yeah we are looking to support most esbuild config for `sst.Function`. Is there any particular configs u need right now? We will prioritize for them.

yeah - <https://github.com/serverless-stack/serverless-stack/issues/1576>

But I'm really curious why Function can't wrap NodejsFunction - is there something so amazingly custom in the bundling step that can't be expressed using the options available to NodejsFunction?

get all the features and bug fixes and dealing with different setups that NodejsFunction has... trying to maintain a parallel version seems like a nightmare. sst.Function <https://serverless-stack.slack.com/archives/C01JG3B20RY/p1648139908292739|doesn't work> for my setup for example