JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 48
  • Score
    100M100P100Q66935F
  • License MIT

Framework to create web apps with any provider. This is the core, you can use it with an official provider implementation or you can implement your own provider.

Package Exports

  • lambda-framework

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (lambda-framework) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Lambda Framework

CII Best Practices Coverage Status Build Status npm version

A framework to create serverless web applications with any provider.

This is the core project, you can use it with an official implementation of a provider or you can implement your own provider. For more information, please keep reading.

The idea behind Lambda Framework is that you can use the features of the framework forgetting the provider you are using. Thus, you can change the provider without change your code base. The only thing you have to do for change the provider is change the lib that implements the one provider for other, but the core will be the same.

Lambda Framework projects

Lambda Framework is very modular. This is because the lambda functions have to be lightweight. You can use the projects you need in your web application.

Features

  • Configurable
  • HTTP requests routing
  • Other events requests routing
  • HTTP helpers (redirection, etc)
  • Templating
  • Error handling
  • For any serverless provider
  • Extensible with modules

How to use it?

Initialize the App

The main object is the App. You have to instantiate a new App object and then you can do what you need with it.

import App, { IApp } from "lambda-framework";

const app: IApp = new App();

A event handling is started passing that event to the App method handle.

app.handle(event, callback);

You don't need to care about passing the event to the App handler, you can use the AWS Lambda implementation or another provider implementation. These will manage the creation of the raw event and passing it to the handler.

import App, { IApp } from "lambda-framework";
import AWSHandler from "lambda-framework-aws";

const app: IApp = new App();
...
export.handler = AWSHandler(app);

Event handling

TODO

HTTP Routing

TODO

HTTP body parsers

TODO

Others HTTP features

TODO

Templating

TODO

More info, API and tutorials

TODO

Contributions

All contributors will be welcome. You can contributing by implementing/fixing/answering one open issue, by suggesting new features for the framework,... For more info about contributing, you can read this.

Make it happen.