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

@mhweiner/aws-tools

v1.0.0

Published

Tools for deploying services to AWS

Readme

aws-tools

A collection of tools for managing AWS infrastructure.

CLI commands

You must first authenticate via aws cli or export keys into shell.

create-stack

./bin/create-stack {STACK_NAME} {TEMPLATE_FILE} {PARAMS_FILE}

Stack name is the name of the stack in CloudFormation. Template file is the path to the CloudFormation template. Params file is the path to the parameters file.

update-stack

./bin/update-stack {STACK_NAME} {TEMPLATE_FILE} {PARAMS_FILE}

Stack name is the name of the stack in CloudFormation. Template file is the path to the CloudFormation template. Params file is the path to the parameters file. There must be changes to the template in order for the stack to update.

redeploy-stack

./bin/redeploy-stack {STACK_NAME} {TEMPLATE_FILE} {PARAMS_FILE}

Redeploys a CloudFormation stack with the given name and template file, using the existing stack's parameters. Useful for updating a stack with a new template without having to specify all the parameters again, or for re-deploying a stack that failed to create for some reason.

Commit Messages

Commit messages are parsed via autorel to determine the version bump, channel/tag, and trigger a release. Commit messages must follow the following rules:

  • Follow the Conventional Commits standard specification (ie, fix: fix a bug, feat: add new feature, feat!: add breaking change)
  • Use one of the following types: build, ci, chore, docs, feat, fix, perf, refactor, revert, style, test.

Here are some examples of commit messages and the resulting SemVer version bump:

  • fix: fix a bug -> 0.0.1
  • feat: add new feature -> 0.1.0
  • feat!: add breaking change -> 1.0.0

By default, the following types do not trigger a version bump or release:

  • build, ci, chore, docs, refactor, style, test

You can find more examples in the Conventional Commits documentation.

Deploying

Every commit made to main that triggers a release per above and passes CI is deployed to production via Github Actions. See the following: