Lambda Wrapper

!GitHub Actions

When writing Serverless applications, we have found ourselves replicating a lot of boilerplate code to do basic actions, such as reading request data or sending messages to SQS. The aim of this package is to provide a wrapper for our Lambda functions, to provide some level of dependency and configuration injection and to reduce time spent on project setup.

If you're coming from v1 and updating to v2, check out the v2 migration guide.

Getting started

Install via npm or Yarn:

``bash
npm i @comicrelief/lambda-wrapper


or


yarn add @comicrelief/lambda-wrapper
`

You can then wrap your Lambda handler functions like this:

`ts
// src/action/Hello.ts
import lambdaWrapper, {
ResponseModel,
RequestService,
} from '@comicrelief/lambda-wrapper';

export default lambdaWrapper.wrap(async (di) => {
const request = di.get(RequestService);
return ResponseModel.generate(
{},
200,
hello ${request.get('name', 'nobody')},
);
});
`

Here we've used the default export lambdaWrapper which is a preconfigured instance that can be used out of the box. You'll likely want to add your own dependencies and service config using the configure method:

`ts
// src/config/LambdaWrapper.ts
import lambdaWrapper from '@comicrelief/lambda-wrapper';

export default lambdaWrapper.configure({
// your config goes here
});
`

configure returns a new Lambda Wrapper instance with the given configuration. You'll want to export it and then use this when wrapping your handler functions.

Read the next section to see what goes inside the config object!

If you want to start from scratch without the built-in dependencies, you can use the LambdaWrapper constructor directly.

`ts
// src/config/LambdaWrapper.ts
import { LambdaWrapper } from '@comicrelief/lambda-wrapper';

export default new LambdaWrapper({
// your config goes here
});
`

Dependencies

Lambda Wrapper comes with some commonly used dependencies built in:

- HTTPService
- LoggerService
- RequestService
- SQSService
- TimerService

Access these via dependency injection. You've already seen an example of this where we got RequestService. Pass the dependency class to di.get() to get its instance:

`ts
export default lambdaWrapper.wrap(async (di) => {
const request = di.get(RequestService);
const sqs = di.get(SQSService);
// ...
});
`

To add your own dependencies, first extend DependencyAwareClass.

`ts
// src/services/MyService.ts
import { DependencyAwareClass } from '@comicrelief/lambda-wrapper';

export default class MyService extends DependencyAwareClass {
doSomething() {
// ...
}
}
`

If you need to override the constructor, it must take a DependencyInjection instance and pass it to super.

`ts
export default class MyService extends DependencyAwareClass {
constructor(di: DependencyInjection) {
super(di);
// now do your other constructor stuff
}
}
`

Then add it to your Lambda Wrapper configuration in the dependencies key.

`ts
// src/config/LambdaWrapper.ts
import lambdaWrapper from '@comicrelief/lambda-wrapper';

import MyService from '@/src/services/MyService';

export default lambdaWrapper.configure({
dependencies: {
MyService,
},
});
`

Now you can use it inside your handler functions and other dependencies!

`ts
// src/action/DoSomething.ts
import lambdaWrapper from '@/src/config/LambdaWrapper';
import MyService from '@/src/services/MyService';

export default lambdaWrapper.wrap(async (di) => {
di.get(MyService).doSomething();
});
`

Service config

Some dependencies need their own config. This goes in per-service keys within your Lambda Wrapper config. For an example, see SQSService which uses the sqs key.

`ts
export default lambdaWrapper.configure({
dependencies: {
// your dependencies
},
sqs: {
// your SQSService config
},
// ... other configs ...
});
`

To use config with your own dependencies, you need to do three things:

1. Define the key and type of your config object.

Using SQSService as an example, we have the sqs key which has the SQSServiceConfig type:

`ts
export interface SQSServiceConfig {
queues?: Record;
queueConsumers?: Record;
}
`

2. Define a type that can be applied to a Lambda Wrapper config.

This simply combines the key and type defined in step 1. Conventionally we name these With... types.

`ts
export interface WithSQSServiceConfig {
sqs?: SQSServiceConfig;
}
`

In the case of SQSService, the sqs key is optional because this dependency is included by default and not all applications need it. If your dependency requires config in order to work, you can make this a required key.

3. In your dependency constructor, cast the config to this type.

`ts
export default class SQSService extends DependencyAwareClass {
constructor(di: DependencyInjection) {
super(di);

const config = (this.di.config as WithSQSServiceConfig).sqs;
// Bear in mind that because the sqs key is optional, the type of
// config will be SQSServiceConfig | undefined. Take care when
// accessing its properties! You can use optional chaining:
const queues = config?.queues || {};
// ...
}
}
`

When you go to configure your Lambda Wrapper, you can now include your dependency's config type in the generic for configure to get IntelliSense completions and type checking for your config keys.

`ts
lambdaWrapper.configure({
sqs: {
queues: 42 // Oops! This will be flagged as a type error by TypeScript
},
});
`

You can combine types for multiple dependencies if needed using &:

`ts
lambdaWrapper.configure({
sqs: {
// SQSService config
},
other: {
// OtherService config
},
});
`

Monitoring

At Comic Relief we use Lumigo for monitoring and observability of our deployed services. Lambda Wrapper includes the Lumigo tracer to allow us to tag traces with custom labels and metrics (execution tags).

Lumigo integration works out-of-the-box with Lumigo's auto-trace feature. If you prefer manual tracing, enable it by setting LUMIGO_TRACER_TOKEN in your Lambda environment variables.

And if you don't use Lumigo, don't worry, their tracer will not be instantiated in your functions and no calls will be made to their servers unless LUMIGO_TRACER_TOKEN is set.

Notes

Lambda Wrapper's dependency injection relies on class names being preserved. If your build process includes minifying or uglifying your code, you'll need to disable these transformations.

In many of our projects we use serverless-webpack to bundle service code prior to deployment. To disable name mangling, set optimization.minimize to false in your webpack config:

`js
// webpack.config.js
module.exports = {
// ...
optimization: {
minimize: false,
},
`

Development

$3

Run yarn test to run the unit tests, and yarn test:types to run the type tests.

When writing a bugfix, start by writing a test that reproduces the problem. It should fail with the current version of Lambda Wrapper, and pass once you've implemented the fix.

When adding a feature, ensure it's covered by tests that adequately define its behaviour.

$3

Run yarn lint to check code style complies to our standard. Many problems can be auto-fixed using yarn lint --fix`.

$3

Release management is automated using semantic-release.