npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@aws-lambda/flow

v0.0.8

Published

A module for simplifying development with aws lambda by providing a pattern for modularizing the pre-processing that typically takes place before core business logic is executed (e.g. initialization, authentication/authorization, http header injection...e

Downloads

4

Readme

npm version Build Status Coverage Status

@aws-lambda/flow

A module for simplifying development with aws lambda by providing a pattern for modularizing the pre-processing that typically takes place before core business logic is executed (e.g. initialization, authentication/authorization, http header injection...etc.)

Installation and Usage

Prerequisites: Node.js >=8, npm version 6+.

You can install the http module using npm:

$ npm install @aws-lambda/flow --save

Basic Flow

The following example shows a lambda flow that adds two handlers before executing the main business logic of the lambda function. This illustrates how one can succinctly reuse common pre-tasks like loading a configuration or publishing a cloudwatch metric:

'use strict';

const Flow = require("@aws-lambda/flow").HTTPFlow;

module.exports.basic = (event, context, callback) => {
  // instantiate new flow object with lambda parameters
  let basicFlow = new Flow(event, context, callback);

  // add common functionality that always occurs before the core business logic
  // (these are fictional handlers used for illustrative purposes)
  basicFlow.add(configLoader);
  basicFlow.add(cloudWatchReporter)

  // add core business logic
  basicFlow.add((event, context, handlerFlow) => {
    // access config that was injected by configLoader
    let dataSource = handlerFlow.state.config.dataSource;
    doDatabaseWork(dataSource);

    // complete the flow
    handlerFlow.success();
  });
};

HTTPLambdaFlow (For http proxy integration where a response should always return an http response)

The following example shows an http lambda flow that adds handlers that are typically used in web flows where an http request needs to be authorized, the request body / paramters need to be parsed, and headers (in this example security headers) need to be added to the response:

'use strict';

const HTTPFlow = require("@aws-lambda/flow").HTTPFlow;

module.exports.hello = (event, context, callback) => {
  let flow = new HTTPFlow(event, context, callback);
  // add an authorizer and security header injector into the flow ()
  flow.add(configLoader);
  flow.add(authorizer);
  flow.add(securityHeaders);
  flow.add(requestValidator);
  flow.add((event, context, handlerFlow) => {
    /* *
     * Since request validation was handled by first flow,
     * we can access the name field directly from the state and
     * add it to the response.
     */
    handlerFlow
      .response
      .body({
        message: "Hello " + handlerFlow.state.name + "!"
      });
    // complete flow with success
    handlerFlow.success();
  });
  flow.execute();
};