Skip to content

CHANGELOG.md

Latest commit

 

History

History
176 lines (114 loc) · 9.3 KB

CHANGELOG.md

File metadata and controls

176 lines (114 loc) · 9.3 KB

@as-integrations/aws-lambda

4.0.1

Patch Changes

  • #197 5ee8ee8 Thanks @jay-l-e-e! - Fixed an issue where Apollo V4 was being installed because peer dependencies were not restricted to Apollo V5.

4.0.0

Major Changes

3.1.0

Minor Changes

  • #122 d1e8271 Thanks @BlenderDude! - Fixes missing decodeURIComponent during GET request parsing of query string for ALB and V1 event

3.0.0

Major Changes

Minor Changes

  • #91 71c94df Thanks @BlenderDude! - ## Short circuit middleware execution

    You can now opt to return a Lambda result object directly from the middleware. This will cancel the middleware chain, bypass GraphQL request processing, and immediately return the Lambda result.

    Example

    export const handler = startServerAndCreateLambdaHandler(
  server,
  handlers.createAPIGatewayProxyEventV2RequestHandler(),
  {
    context: async () => {
      return {};
    },
    middleware: [
      async (event) => {
        const psk = Buffer.from('SuperSecretPSK');
        const token = Buffer.from(event.headers['X-Auth-Token']);
        if (
          psk.byteLength !== token.byteLength ||
          crypto.timingSafeEqual(psk, token)
        ) {
          return {
            statusCode: '403',
            body: 'Forbidden',
          };
        }
      },
    ],
  },
);

2.0.1

Patch Changes

2.0.0

Major Changes

  • #67 5669d23 Thanks @BlenderDude! -

    Why Change?

    In the interest of supporting more event types and allowing user-extensibility, the event parsing has been re-architected. The goal with v2.0 is to allow customizability at each step in the event pipeline, leading to a higher level of Lambda event coverage (including 100% custom event requests).

    What changed?

    The second parameter introduces a handler that controls parsing and output generation based on the event type you are consuming. We support 3 event types out-of-the-box: APIGatewayProxyV1/V2 and ALB. Additionally, there is a function for creating your own event parsers in case the pre-defined ones are not sufficient.

    This update also introduces middleware, a great way to modify the request on the way in or update the result on the way out.

    startServerAndCreateLambdaHandler(
  server,
  handlers.createAPIGatewayProxyEventV2RequestHandler(),
  {
    middleware: [
      async (event) => {
        // event updates here
        return async (result) => {
          // result updates here
        };
      },
    ],
  },
);

    Upgrade Path

    The upgrade from v1.x to v2.0.0 is quite simple, just update your startServerAndCreateLambdaHandler with the new request handler parameter. Example:

    import {
  startServerAndCreateLambdaHandler,
  handlers,
} from '@as-integrations/aws-lambda';

export default startServerAndCreateLambdaHandler(
  server,
  handlers.createAPIGatewayProxyEventV2RequestHandler(),
);

    The 3 event handlers provided by the package are:

    • createAPIGatewayProxyEventV2RequestHandler()
    • createALBEventRequestHandler()
    • createAPIGatewayProxyEventRequestHandler()

    Each of these have an optional type parameter which you can use to extend the base event. This is useful if you are using Lambda functions with custom authorizers and need additional context in your events.

    Creating your own event parsers is now possible with handlers.createRequestHandler(). Creation of custom handlers is documented in the README.

1.2.1

Patch Changes

1.2.0

Minor Changes

Patch Changes

1.1.0

Minor Changes

Patch Changes

1.0.1

Patch Changes

1.0.0

Major Changes

0.1.1

Patch Changes

  • #20 8ae797f Thanks @trevor-scheer! - Update AS dependencies which incorporate a new response shape for supporting incremental delivery (which will not be supported by serverless integrations like this one)

0.1.0

Minor Changes