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

lambda-executor

v0.1.0

Published

A library to easily execute lambda functions

Downloads

16

Readme

Lambda Executor

Travis npm

A library to easily execute AWS lambda functions from JavaScript code.

How it works

Pass the lambda function file name and event object to this tester. The lambda function will be executed either

  • in a separate process with limited time and memory, the same way it is executed in the lambda environment
  • in the same process just limited by time

Install

npm install lambda-executor --save-dev

Usage

API

lambdaTester(fileName, handlerName, event, timeout, memory, callback, sameProcess, babel)

  • fileName : absolute filename of lambda function
  • handlerName : name of exported handler function (default: handler)
  • event : JSON event object
  • timeout : timeout in milliseconds
  • memory : maximum available memory in MB
  • callback(err, result) : callback function which is executed after execution completed
  • sameProcess (optional) : boolean if executor should not create a separate child process to execute the function (default: false)
  • babel (optional) : boolean if babel should be registered to execute es2015 code (default: false)

Example

var lambdaExecutor = require('lambda-executor');
var path = require('path');

describe('My Tests', function() {
  it('should succeed', function(done) {
    lambdaExecutor(path.join(__dirname, 'function.js'), 'handler', {}, 10, 128, function(err, result) {
      //insert assertions here
      done();
    });
  });
});

Modes

Different process (default)

By default functions are executed in a different process. This makes the execution very similar to how it is executed on AWS. However, in this mode you can only return plain objects (without any functions) from the function. The executer uses communication via process messages which can only plain objects (https://nodejs.org/api/child_process.html#child_process_event_message). Also it is not possible to record code coverage if the function is executed in a separate process.

Same process

If you use the local mode you can return anything from the lambda function (including Error objects). Also code coverage can be recorded. However, the execution won't stop if the function consumes more memory then specified.

License

MIT