serverless-microservices-graphql-template VS serverless-esbuild

For those that know me, they know I love talking about two things more than anything: Serverless Framework and GraphQL. Today, I'm excited to announce a project starter template that I've been developing that allows developers to build serverless microservices with GraphQL. It is built using Nx monorepos and provides a lot of quality of life developer tooling out-of-the-box. I'll discuss what's in the repo and how you can leverage it today for your own projects. If you want to jump into the code, you can find it on GitHub.

Support Yarn PnP with externals bundling #327

We use serverless-esbuild to transpile our TypeScript code to JavaScript.

You should use appropriate tools to bundle your Lambda functions with a minimal size. For example, the Serverless Framework, with the serverless-esbuild plugin, automatically bundles your code and uploads it to AWS.

One of the most important aspects of serverless development is keeping an eye on your bundle sizes and to reduce cold start times on Lambda. Keeping this in mind, the template utilizes serverless-esbuild and serverless-analyze-bundle-plugin to provide function analysis out-of-the-box. I opted for serverless-esbuild over serverless-bundle for a few reasons:

Its faster and easier to setup that webpack and drastically reduces the size of the archive. For Serverless framework users there is https://github.com/floydspace/serverless-esbuild and if you use SAM CLI, you already get this for free since they now use esbuild in the build process

if you can, try using https://github.com/floydspace/serverless-esbuild - esbuild is stupid fast and it produces tiny artifacts. Its dead simple too compared to the webpacks/rollups/etc.