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-local

v2.0.6

Published

Run AWS Lambda functions locally! The most lightweight library - no external dependencies. Only 100 lines of code.

Downloads

592

Readme

aws-lambda-local

Run AWS Lambda function locally! The most lightweight library - no external dependencies. Less than 200 lines of code.

Windows, Mac and Linux tested!

Installation

npm install -g aws-lambda-local

Inputs

-f functionName     | --function=functionName       required       Path to Lambda function main file
-e event            | --event=event                 optional       Either path to .json file contains event object or raw JSON data
-c contextPath      | --context=contextPath         optional       Path to .json file contains context object
-t seconds          | --timeout=seconds             optional       Force quit Lambda function after XX seconds
-h handler          | --handler=exports.handler     optional       Module.exports.handler name. Default is first function from the module 

Usage

Just specify function name (can be in nested directory), event object file. Optionally you also may replace default context object and timeout (30 seconds by default).

$ cat function.js

exports.handler = function(event, context)
{
    context.done(event, context);
    // or
    return new Promise((resolve, reject) => {})
};

Or

exports.handler = function(event, context, callback)
{
    callback(null, dataToRetun);
};

Or

exports.handler = function(event)
{
    return new Promise((resolve, reject) => {})
};

Or even

exports.handler = async (event) =>
{
    return 'ret';
}

Check the event object. You can create any set of input data (and use them for functional testing or something else)

$ cat event.json
{
    "obj"   : { "a" : "b" },
    "int"   : 1,
    "str"   : "qwerty",
    "arr"   : [ 1, 2, 3, 4 ]
}

$ lambda-local -f function -e event.json -t 20
ERROR
--------------------------------
{
    "obj": {
        "a": "b"
    },
    "int": 1,
    "str": "qwerty",
    "arr": [
        1,
        2,
        3,
        4
    ]
}
OUTPUT
--------------------------------
{
    "awsRequestId": "wn26j4dm-m8zd-d7vi-j94j-50t4zsjlwhfr",
    "logGroupName": "/aws/lambda/function",
    "logStreamName": "2015/11/12/[$LATEST]wn26j4dmtm8zd7vij94j50t4zsjlwhfr",
    "functionName": "function",
    "memoryLimitInMB": "128",
    "functionVersion": "$LATEST",
    "invokedFunctionArn": "arn:aws:lambda:aws-region:1234567890123:function:function",
    "invokeId": "wn26j4dm-m8zd-d7vi-j94j-50t4zsjlwhfr"
}

Other ways to pass the input event:

$ lambda-local -f function -e event.json
$ lambda-local -f function -e '{"json":"here"}'
$ cat event.json | lambda-local -f function
$ echo '{"json":"here"}' | lambda-local -f function

CLI script will return non-zero exit code (1) in case of any failure.

If you missed to call context.succeed()|fail()|done() function and your Lambda function runs forever - just use timeout option!

Check out my aws-lambda-build package!