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

lambdr

v0.0.5

Published

Lambdr ====== Lambdr is automated deployment and flow management module to create powerful micro services with AWS Lambda functions. It's still in development and looking for contributors. 🤘

Downloads

15

Readme

Lambdr

Lambdr is automated deployment and flow management module to create powerful micro services with AWS Lambda functions. It's still in development and looking for contributors. 🤘

Getting Started

First we need to install cli globally.

npm install lambdr -g

Creating a project

Assume that a lambdr project as a micro service.

lambdr new my-micro-service

This will create a folder named 'my-micro-service' and it includes the following files:

my-micro-service
|-- config
|   |-- aws.json (AWS credentials)
|   |-- env.json (Environment variables for every stage)
|   |-- lambdr.json (Lambder configurations)
|-- functions
|   |-- .... (You lambda functions will be here)
|-- package.json
|-- .gitignore

Creating a function

Let's create a signup function. After you enter the command the cli will ask you the HTTP method for the function and the endpoint.

We can use POST method and /users endpoint for signup function.

lambdr function:create signup

After the command finishes, a js file will be added into functions folder.

Running a function locally

It's really easy to run the function in your local machine by using this command:

lambdr function:run signup

Before running a function you can pass event parameters by changing testEvents function property in config/lambdr.json.

{
  "accountId": "123456789",
  "name": "my-micro-service",
  "functions": {
    "signup": {
      "method": "POST",
      "endpoint": "/users",
      "testEvent": {
        "email": "test@example.com",
        "password": "incredible_password"
      }
    }
  }
}

Create a stage

To deploy your functions you need to create a stage. You can create multiple stages like (development, staging, production).

Assume we want a development stage for now.

lambdr stage:create development

Deploy a function

lambdr function:deploy signup development

We deployed signup function into development stage. After this command you will see an endpoint to test this function.

Using environment variables

Lambdr deploys environment variables for it's own stage. You can set environment variables in config/env.json file. An example env.json:

{
  "default": {
    "APP_NAME": "Example OAuth Micro Service",
    "TEST_STAGE": true
  },
  "local": {
    "DYNAMO_TABLE": "users-local"
  },
  "development": {
    "DYNAMO_TABLE": "users-dev"
  },
  "production": {
    "TEST_STAGE": false
  }
}

Notice that TEST_STAGE will be overridden in production stage.

exports.handler = function(event, context) {
  if (process.env.TEST_STAGE) {
    context.done(null, 'This stage is for testing');
  } else {
    context.done(null, 'This stage is production');
  }
}

Other Commands

List stages

lambdr stage:list

Remove a stage

lambdr stage:remove staging