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

@gidw/aws-lambda-deploy

v1.0.4

Published

Helper module for deploying AWS Lambda functions in Node.js.

Downloads

5

Readme

aws-lambda-deploy

Usage

gald [command] [option]

There are 3 commands available

gald init
gald test
gald deploy

Commands

init

Create (missing) configuration files that provide information to the module about the AWS Lambda function.

After running init you should consider adding lambda-secrets.json to your .gitignore.

The Handler property consists of the module name and the function name.

For example a file handler.js with:

exports.myHandler = function () {};

The resulting Handler property looks like this:

"Handler": "handler.myHandler"

test

Execute all defined tests in lambda-test.json or a different JSON file.

gald test [optional json file]

deploy

Deploys the Lambda function to AWS Lambda. In case the Lambda function does not exist or the configuration has been changed, the user will be notified.

Deploy looks for the archive defined in lambda-config.json under the property archiveName. Your build system will have to provide a zip file with the necessary components for the AWS Lambda function.

For example, have a build script that looks like this:

zip -r -9 archive.zip handler.js

If your AWS Lambda function depends on other packages, make sure to include the node_modules folder, with the dependencies installed, in your zip file.