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

deploy-s3

v0.1.1

Published

Deploy front end apps to S3

Downloads

10

Readme

Deploy S3

Build Status

Usage

Install with npm:

npm i --save deploy-s3

In your package.json, you must have the following properties defined:

"name": "oms-ui"
"deploy": "myDeployDirectory/"

In a file or in env variables, you must have the credentials for using S3:

{
    "key": "somestring",
    "secret": "somebigstring"
} 

In your task runner, create a knox-compatible S3 client and deploy:

S3Deployer = require 'deploy-s3'

# Read your package.json file
pkg = JSON.parse fs.readFileSync './package.json'

# Read your access key and secret key
credentials = JSON.parse fs.readFileSync '/credentials.json'

# Choose your bucket
credentials.bucket = 'vtex-io'

# Create a client with your credentials
client = knox.createClient credentials

# Create a new S3Deployer 
deployer = new S3Deployer(pkg, client)

doneHandler = -> console.log 'Done'
failHandler = console.error
progressHandler = console.log

# deploy() returns a promise and notifies of each uploaded file
deployer.deploy().then doneHandler, failHandler, progressHandler

This will cause every file under myDeployDirectory/ to be deployed to the vtex-io bucket under the oms-ui directory.

If your doneHandler is called, that means your deploy is complete.

Options

S3Deployer accepts a third parameter with options:

dryrun: if upload should be skipped. Defaults to false.
chunk: how many files to upload in parallel. Defaults to 20.
batchTimeout: timeout for entire upload. millis. Defaults to 1000 * 60 * 5.
fileTimeout: timeout for upload of each file. millis. Defaults to 1000 * 30.