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

aws-webdeploy

v2.1.5

Published

Commandline tool used to deploy a web application.

Downloads

10

Readme

aws-webdeploy

Tiny utility to allow configuring a web application deployment from your package.json and leverage AWS-CDK.

NPX Usage (Option 1)

Add the webdeploy section to your package.json file. (see below for more options)

  "webdeploy": {
    "distPath": "./dist",
    "resourcePrefix": "test-web-stack"
  }

Then just do this:

npx aws-webdeploy

Integrated as npm-script (Option 2)

TLDR; Install this along with the AWS CDK CLI (installed globally) and you can yarn deploy your static website out of your dist directory.

Full example project

https://github.com/dsandor/aws-webdeploy-example

asciicast

What are the pre-requisites?

package.json webdeploy settings

In its simplest form you only need to add the following section to your package.json file. Here you are specifying the location of your static website files ./dist/ in this case. You are also specifying a prefix to use for your AWS Resources in the CloudFormation stack. This should be a unique prefix to avoid collision with your S3 bucket name. Pick something like www-mywebsite-com which is unique and descriptive.

  "webdeploy": {
    "distPath": "./dist",
    "resourcePrefix": "test-web-stack"
  }

Add the deploy script to your package.json

Add the following to your package.json file:

  "scripts": {
    "deploy": "cdk deploy --app node_modules/aws-webdeploy/deploy.js"
  },

How to deploy?

yarn deploy

-or-

npm run deploy

This kicks off the cdk deploy command and uses a small cdk app that will use the parameters you configured in your package.json file.

Full package.json file settings

|property|description| |---|---| |websiteDistPath|The HTML files to be deployed. e.g. ./dist| | deploymentVersion|A version number for your deployment.| | resourcePrefix|Used to group resources with a prefix. The S3 bucket is prefixed with this value.| | indexDocument|index document for your website. default: index.html| | certificateArn|the ARN for the SSL certificate for your website. (optional)| | domainNames|an array of strings representing your website domain name (must match the certificate) e.g. ['mydomain.com', 'www.mydomain.com']|

Please note that if you wish to use your own domain names and not just the Cloud Front Distribution URL you will also need a certificate. It is very simple to create a certificate in AWS console and it is free (assuming you are supporting modern browsers only). Once you have the ARN for your certificate use the certificateArn property. You will also need to provide the domain names to the domainNames property. The domain names MUST MATCH the domain names you put on your certificate.

What gets created for me?

  • CloudFront Distribution
  • CloudFront Origin that maps to a versioned folder in an S3 bucket
  • Correct permissions to disallow public access to the S3 bucket.
  • Correct permissions for CloudFront to serve the files from S3
  • S3 Bucket for the website assets (placed into a folder based on deploymentVersion value)