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 🙏

© 2026 – Pkg Stats / Ryan Hefner

baryon

v0.0.8

Published

Simple AWS Lambda deployment command line interface

Readme

Baryon

Simple command line AWS Lambda Function deployment system.

baryon

Install

To install baryon, run:

npm install baryon -g

Deploy Lambda Functions

See below for setup.

To deploy all your Lambda functions (create new, update changed) run:

baryon deploy

Creating the baryon.json file

Run the interactive init utility:

baryon init

Or you can manually create the needed configuration file in your project root (baryon.json):

{
    "AWS_ACCOUNT_ID": "123456789456",
    "LAMBDA_PREFIX": "MyPrefix",
    "LAMBDA_ROLE": "MyLambdaRole",
    "LAMBDA_REGION": "us-west-2",
    "LAMBDA_RUNTIME": "nodejs4.3",
    "LAMBDA_MEMORY": "256",
    "LAMDBA_TIMEOUT": 3,
    "LAMBDA_HANDLER": "index.handler"
}

Configuration file (baryon.json) Params:

|Config Param |Description | |-------------------|:-----------------------------------------------------------| |AWS_ACCOUNT_ID |Your Amazon AWS account number | |LAMBDA_PREFIX |Prefix that all the Lambda directories/functions start with | |LAMBDA_ROLE |Name of the role that the Lambda function will use | |LAMBDA_REGION |AWS region to deploy the Lambda functinos in |

Folder Structure

The basis of this deployment system depends on a properly formatted folder structure. Each of the Lambda folders in your project will have to have a defined prefix. The complete folder name will be the name of the deployed Lambda function (i.e. the folder "AwesomeLambdaFunction" will be deployed as "AwesomeLambdaFunction" the function).

Here's an example baryon project folder structure:

$ tree myLambdaProject -I node_modules
myLambdaProject/
├── MyPrefixChangePassword
│   └── index.js
├── MyPrefixCreateUser
│   └── index.js
├── MyPrefixLoginUser
│   ├── config.json
│   └── index.js
├── MyPrefixLostPassword
│   └── index.js
├── MyPrefixVerifyUserEmail
│   └── index.js
├── baryon.json
└── package.json

Bundling node_modules Into Functions

You can bundle individual node_modules into your Lambda function by adding a config.json file that contains the desired packages to the Lambda folder.

The config.json should look something like this (bundle is an array of package names):

{
  "bundle": [
    "async",
    "gm"
  ]
}

NPM Install Bundling

Bundling node_modules into functions will not work with the newer npm install bundling strategy. If you have a newer version of node, you will want to use the --legacy-bundling flag to install all the needed sub dependencies in with the package.

Example:

npm install --legacy-bundling lodash