aws-sam-cli VS esbuild

aws-sam-cli-linux

Does anyone have any success with API Gateway/Lamba for local environment with hot-reloading? I was playing around with “sam local start-api” a few weeks ago with along with CDK but it doesn’t seem like hot-reloading is supported, and need to manually restart for code changes to reflect, which is currently stopping me from trying out the API Gateway/Lamba combo further due to inefficient DX. Here’s a GitHub issue about it: https://github.com/aws/aws-sam-cli/issues/901

Mostly due to lack of proper documentation it was difficult to get the HTTPApi syntax correct. The yaml file is very picky for CORS configuration on an HTTPApi. Luckily I found this github issue which allowed me to troubleshoot my yaml file.

No, it's not just muscle memory. It doesn't work with podman. That's what I'm talking about https://github.com/aws/aws-sam-cli/issues/1668

AWS SAM CLI with the support of Typescript is still in Beta. If you want more advanced features maybe you should not use it. Lately, in version 1.49.0 External and Loader properties have been added. If you want to share your feedback and/or requests this issue has been created.

I spent a while creating a custom runtime to use the native-image agent to harvest config from my Lambda, and then patching sam cli to work in Docker user networks... after pushing through all that, I still didn't get a working build - the native-image compiler just doesn't support everything (or didn't support my feature set, at the time - there has been a new release since then). In my case I think it was Guice that defeated me.

SAM support for TypeScript has been lagging for some time, but a pull request was just merged that should change that. It looks like we'll be able to add an aws_sam key in the package.json file to enable building within the SAM engine as part of sam build. Although this PR has been merged to aws-lambda-builders, the engine behind sam build, it will still need to be added to aws-sam-cli and released (to much fanfare, one expects) before it can be used with SAM.

I am installing SAM CLI on windows and its super simple. All I need to do is Click on this MSI installer.

sem-version java 8 wget https://github.com/aws/aws-sam-cli/releases/latest/download/aws-sam-cli-linux-x86_64.zip unzip aws-sam-cli-linux-x86_64.zip -d sam-installation sudo ./sam-installation/install checkout cd java-app-backend cache restore build-java-app-backend-$SEMAPHORE_GIT_BRANCH sam deploy --no-confirm-changeset --stack-name serverless-web-application-java-backend --capabilities CAPABILITY_AUTO_EXPAND CAPABILITY_IAM

During my search for deploying Lambdas via GitHub actions, I came across a tutorial that utilized ncc for converting TypeScript and bundling. While ncc is effective, I discovered esbuild, which proved to be significantly faster and perfectly suited to my requirements.

The advent of esbuild, the native support for ES Modules in browsers, the widespread adoption of import map, the emergence of tools like Native Federation, and the Nx ecosystem all combine to forge a flexible and well-maintained Micro Frontend Architecture.

EsBuild is a relatively new, blazing-fast JavaScript bundler and minifier. It stands out for its high performance, significantly speeding up the build process in development pipelines.

Unlike Webpack, the Vite DevServer only compiles files when they are requested. It leverages ES module imports, which allow JS files to import other files without needing to bundle them together during development. When one file changes, only that file needs to be re-compiled, and the rest can remain unchanged. Project files are compiled with Rollup.js. Third-party dependencies in node_modules are pre-compiled using the ultra-fast esbuild bundler for maximum speed, and they are cached until the dependency version changes. Vite also provides a client script for hot module reloading.

Use esbuild to build the React code into a form executable on both the server and client sides.

The functions will bundle using esbuild. For that, it is required to install esbuild globally:

TSX is the newest and most improved version of our ts-node, using ESBuild to transpile TS files to JS very quickly. The most interesting part is that TSX was developed to be a complete replacement for Node, so you can actually use TSX as a TypeScript REPL, if you install it globally with npm i -g tsx, just run tsx in your terminal and you can write TSX natively. But what's even cooler is that you can load TSX for all TypeScript files using --loader tsx when you run your file. For example, let's say we have this file called index.ts:

esbuild plus Vite is out of developer preview and enabled by default, yielding 67%, 87%, 80% speed improvements for build time, hybrid build time and hybrid serve time respectively.

Bundling with esbuild

Besides Webpack, there are many other popular web bundlers available, such as Parcel, Esbuild, Rollup, and more. They all have their own unique features and strengths, and you should make your decision based on the needs and requirements of your specific project. Please refer to their official websites for details.