Repository navigation
example: add Bun Hono example - #876
Conversation
Run a Hono app on Bun in a container image behind Lambda Web Adapter. The Dockerfile installs Bun with npm on the Node.js image from ECR Public, because Bun has no official image there. Add the example to the image matrix so Verify Examples builds and boots it, and claim its manifest in dependabot.yml.
|
I refreshed the branch from upstream and kept the existing maintainer merge commit. The example files are unchanged. Fresh core CI passed 98 tests and both layer builds. All 19 runtime checks passed, including this Hono example. The global template validator still fails on the unchanged Could you approve the fresh upstream workflow runs? Thank you! |
bnusunny
left a comment
There was a problem hiding this comment.
Thanks @mattenarle10, nice example. It uses ECR Public only (per #752), a frozen lockfile and --production installs, the transpiler cache is off for the read-only filesystem, and it doesn't echo the full contexts. sam validate --lint and check-example-config.sh pass locally, and the lockfile has no known advisories.
The validate failure on fastapi-response-streaming-lmi is pre-existing on main.
Issue #, if available: N/A
Description of changes:
This PR adds
examples/bun-hono. It runs a Hono application on Bun in a container image with Lambda Web Adapter. The application is a Bun HTTP server in TypeScript with no build step.Changes:
examples/bun-hono: the application, the Dockerfile, the SAM template, and a README..github/example-matrix.json: animageentry, so Verify Examples builds and boots the example..github/dependabot.yml: an npm entry for/examples/bun-hono/app.README.mdanddocs/guide/src/examples/overview.md: the example is in the two lists.The Dockerfile starts from the Node.js image on Amazon ECR Public and installs Bun with npm. Bun has no official image on ECR Public, and the examples do not pull from Docker Hub (#752).
GET /returns the request ID and the function name, not the full request context and Lambda context. The full contexts contain the AWS account ID.This is a companion to #875 (Hono in Zip). The two PRs do not change the same lines.
Original verification (October 9):
check-example-config.shandsam validate --lintpass.test-image (bun-hono)job: https://github.com/mattenarle10/aws-lambda-web-adapter/actions/runs/37814634690GET /andGET /hello/lambdareturn 200.Refresh verification (2026-11-09)
I merged upstream
b6a089band kept the existing maintainer merge commit. The example files are unchanged.The example workflow remains red because its global template validator fails with E6101/E1010 on
examples/fastapi-response-streaming-lmi/template.yaml. That template and its validation workflow are unchanged from upstream.I also checked the app routes, context headers, 404s, shutdown, local SAM validation, and a read-only non-root container. The original AWS deployment verification above was on October 9. I did not deploy AWS resources for this refresh.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.