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

@whatskit/s3deployer-cli

v0.1.2

Published

Use this tool to deploy a SPA to AWS with CI or manually.

Readme

@whatskit/s3deployer-cli

Use this tool to deploy a SPA to AWS with CI or manually.

Features:

  • Targeted CloudFront invalidation and caching
  • CircleCI, Bitbucket, and GitHub Actions examples
  • Embedded Globals and Build uplifting ( dev -> stg -> prd )

Examples:

Setup

yarn add -D @whatskit/s3deployer-cli

Full config.yaml

Please see the examples for sane defaults!

stages:
  myapp-dev: # one stage per deploy
    spaDeploy:
      verbose: false
      buildPath: "./dist"
      includeGlob: "**"
      ignoreGlob:

      aws:
        region: us-east-1
        accountId:

      s3:
        acl: "public-read"
        bucket: myapp-dev-website
        prefix:
        purge: false
        force: false
        invalidateGlob: # extra glob for invalidation

      cloudfront:
        distributionId:
          - CF324365475432
        invalidatePaths:

      releaseStrategy:

    spaIndexGlob: index.html

    # inject variables into the website
    spaGlobals:
      # APP_STAGE: automatic via stage
      # APP_VERSION: automatic via appVersion option
      # APP_RELEASE: automatic via git

    ## dotenv overrides
    # envFiles: [ '.env.myapp-dev.secrets' ]
    ## environment overrides
    # environment:
    #  app__spaDeploy__s3__bucket: myapp-dev-website

Injecting globals

Add this snippet to the head section in the main index.html. The content will be replaced with spaGlobals in the environment at build time.

<script id="env-data">
  // you can add local testing variables here,
  // this will get overwritten at build
  window.APP_STAGE = "myapp-stg";
</script>

Local Deploy

Check the examples for CI deploy strategies or you can manually deploy with setting up the AWS environment:

config.local.yaml (don't forget to gitignore!)

stages:
  myapp-dev:
    environment:
      AWS_ACCESS_KEY_ID:
      AWS_SECRET_ACCESS_KEY:
yarn s3deployer-cli deploy --stage myapp-stg --appVersion 0.0.1

s3deployer-cli deploy

Descriptions for useful flags. Use --help for a comprehensive list

--stage

The slug of the deployment (ie. prd/stg/dev). Used in config.yaml.

--appVersion

Version of the deploy. Tied to a specific Release and Stage. If supplied with a semver format, the version will be prefixed with ${STAGE}

--ignoreGitChanges

Use this flag while debugging the build. This might have unintended consequences - never deploy a build made using this flag.

--verbose

Display more output

Development

Test locally

# test with ts-node
yarn test:ts-node:cli --help

# build new version
yarn build

# test build
yarn test --help