https://github.com/lukeshay/buntime

An AWS Lambda runtime for Bun
https://github.com/lukeshay/buntime

aws aws-lambda bun

Last synced: about 4 hours ago
JSON representation

An AWS Lambda runtime for Bun

• Host: GitHub
• URL: https://github.com/lukeshay/buntime
• Owner: lukeshay
• Created: 2023-01-15T19:02:37.000Z (almost 2 years ago)
• Default Branch: main
• Last Pushed: 2023-12-15T17:39:51.000Z (11 months ago)
• Last Synced: 2024-04-30T10:26:10.957Z (6 months ago)
• Topics: aws, aws-lambda, bun
• Language: Shell
• Homepage:
• Size: 49.8 KB
• Stars: 2
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Buntime

An AWS Lambda runtime for [Bun](https://bun.sh/)

This exposes the same API as the Node.js runtime. If you are looking how to handle different events, you can refer to AWS documentation. The only difference is we do not support callbacks and the following properties on the context object:

- `context.callbackWaitsForEmptyEventLoop`

- `context.done`

- `context.fail`

- `context.succeed`

## Getting Started

### Prerequisites

Add these secrets to the repository. They must have access to publish lambda layers:

- `AWS_ACCESS_KEY_ID`

- `AWS_SECRET_ACCESS_KEY`

1. Clone or fork this repository

2. Go to the Actions tab

3. Select the action name `Publish Layer`

4. Run the workflow with your desired parameters

## Example lambda handler

```ts

import type {

  APIGatewayProxyEventV2,

  APIGatewayProxyResultV2,

  Context,

} from "aws-lambda";

export default {

  handler(

    event: APIGatewayProxyEventV2,

    context: Context

  ): APIGatewayProxyResultV2 {

    return {

      statusCode: 200,

      headers: {

        "Content-Type": "text/html",

      },

      body: "Hello from Buntime!",

    };

  },

};

```

## Tips

### Testing locally

An example can be found in <`./examples/local.ts`>. In this example, it imports the handler from <`./examples/handler.ts`> and calls it in a simple HTTP server.

### Getting the trace id

We dynamically set the trace id environment variable so you _**MUST**_ access it using `process.env._X_AMZN_TRACE_ID`. `Bun.env._X_AMZN_TRACE_ID` will not work.

## Resources

-