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 🙏

© 2025 – Pkg Stats / Ryan Hefner

lambda-running

v0.2.8

Published

Library for running and testing AWS Lambda functions locally with custom events

Downloads

635

Readme

🚀 Lambda Running

Version License

Run & test AWS Lambda functions locally with ease!

✨ What is Lambda Running?

Lambda Running is a powerful library that lets you test AWS Lambda functions locally without any complicated setup. Perfect for developers who want to iterate quickly and test their Lambda functions in a realistic environment.

🎯 Key Features

  • UI Mode - Beautiful web interface with real-time logs
  • Interactive Mode - Simple CLI for quick testing
  • Custom Events - Test with your own JSON payloads
  • Zero Configuration - Works out of the box
  • TypeScript Support - Including path aliases (@/*)
  • Environment Variables - Automatic loading from .env files

🖥️ UI Mode (Recommended)

Start the UI mode with a simple command:

# Install globally
npm install -g lambda-running

# Start UI mode
lambda-run ui

UI Mode gives you:

  • 🎨 Modern web interface for testing Lambda functions
  • 📊 Real-time logs and execution results
  • 🔍 Enhanced error visualization and stack traces
  • 💾 Save and reuse test events for quick iterations

💻 Interactive Mode

If you prefer the command line:

# Start interactive mode
lambda-run i

# Or run directly
lambda-run run path/to/handler.js handler --event '{"key": "value"}'

🛠️ Quick Usage Guide

  1. Install:

    npm install -g lambda-running
  2. Start UI Mode:

    lambda-run ui
  3. Or Use Interactive Mode:

    lambda-run i
  4. Direct Command:

    lambda-run run ./src/handler.js handler --event '{"userId": "123"}'

🔧 Configuration

Lambda Running works with zero configuration, but you can customize:

  • .env files - Automatically loaded
  • .lambdarunignore - Skip directories during scanning
  • Custom timeouts, ports, etc. via environment variables

📦 Lambda Layers

Enable AWS Lambda layers support by creating a lambda-running.json file in your project root:

{
  "layerMappings": {
    "/opt/nodejs": "layers/common",
  },
  "envFiles": [
    ".env",
    ".env.local"
  ],
  "ignorePatterns": [
    "**/*.test.js",
    "**/__tests__/**"
  ],
  "debug": false
}

This will automatically map /opt/nodejs to ./layers/common in your project.

Your local project structure should match this structure:

my-project/
├── lambdarunning.config.json
├── handler.js (imports from /opt/nodejs/...)
└── layers/
    └── common/
        └── utils/
            └── index.js

⚠️ Important: Lambda Layers support currently only works for local development. You must download the layer code and place it in your project directory as shown above. This feature does not fetch layers from AWS cloud.

Configuration Options

| Option | Type | Default | Description | |--------|------|---------|-------------| layerMappings | Object | {} | Detailed mappings from Lambda layer paths to local directories | | envFiles | Array | ['.env'] | List of environment files to load (in order of precedence) | | ignorePatterns | Array | [] | Additional glob patterns to ignore when scanning for handlers | | ignoreLayerFilesOnScan | Boolean | true | Whether to ignore files in the layers directory when scanning for handlers | | debug | Boolean | false | Enable debug mode for detailed logging |

📚 Learn More

For detailed information, check out:

📝 License

MIT © Nicolás Montoya