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-continuous-delivery

v1.0.3

Published

This module goal is to deploy: - CloudFormation Stacks - Lambda Functions

Downloads

7

Readme

lambda-continuous-delivery

This module goal is to deploy:

  • CloudFormation Stacks
  • Lambda Functions

###Function flow:

  1. Generate package: Finds recursively in each folder the file "package.json", if it's found, a deploy script is generated for that lambda function.
  2. Execute NPM Scripts: Executes the script generated in the previous process.
  3. Deploy Lambda Code: Generates a zip for each lambda function, then uploads it to S3 and finally deletes the zip.
  4. Deploy CloudFormation Stack: Find all .json files in the folder where the stacks are saved and uploads it to S3.

###Deploy script

  1. cd "Lambda folder": Move to the lambda function folder.
  2. npm install: Install every package.
  3. npm run cover: Execute tests and coverage report.
  4. npm prune --production: Remove dev dependencies.

###Configurable parameters All parameters are setted as environment variables

  • ROOT_PATH: Path of the root folder.
  • GIT_BRANCH: Current branch.
  • DEPLOY_BRANCHES: Branches that will trigger the deploy process, seperated by comma and whitout white spaces.
    • Default:
      • "origin/development"
      • "origin/staging"
      • "origin/master"
  • NAME_BRANCHES: Names of the branches to be used in the deploy script, need to be in the same order as the DEPLOY_BRANCHES
    • Default:
      • "development"
      • "staging"
      • "production"
  • AWS_ACCESS_KEY_ID: AWS access key id.
  • AWS_SECRET_ACCESS_KEY: AWS secret key.
  • S3_BUCKET_CODE: Bucket to deploy the lambda functions.
  • S3_BUCKET_CF: Bucket to deploy the CloudFormation stacks.
  • REGION: AWS Region.
  • LAMBDA_PATH: Folder containing the lambda functions.
    • Default: ROOT_PATH + /lambda
  • CF_PATH: Folder containing the CloudFormation stacks.
    • Default: ROOT_PATH + /provisioning
  • EXCLUDE_FOLDER: Folders that will'nt be checked for package.json, separated by comma and whitout white spaces.