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

@cdk-turnkey/stackname

v2.1.0

Published

Get a name for a CDK stack based on GITHUB_REPOSITORY and GITHUB_REF in the environment

Readme

stackname

Print a name for a deployable CDK stack.

The environment variables GITHUB_REPOSITORY and GITHUB_REF should be set as is done in GitHub Actions.

Why

So you can vary the name of your CloudFormation stack, built with the CDK, and always know what the stack's name will be. You want to vary the stack name by the repo and branch, so that you can deploy different repos in the same account, and different branches of the same repo to the same account. You want to always know what the stack's name will be so that you can ask a question like, "What's the frontend S3 bucket name for this environment?" In that sense it's more like "envname" than "stackname," but it's called "stackname."

How

$ npx @cdk-turnkey/stackname --help
Usage: @cdk-turnkey/stackname [options]

Print a name for an AWS CDK stack based on environtment variables GITHUB_REPOSITORY, GITHUB_REF, and an optional suffix. `GITHUB_REPOSITORY=my-Name/myRepo GITHUB_REF=refs/heads/myBranch npx @cdk-turnkey/stackname --suffix StackOne` prints My-nameMyrepoMybranch-StackOne.

Options:
  -V, --version          output the version number
  -s, --suffix <SUFFIX>  A suffix to append to the stackname after a dash (-) (default: "")
  -h, --help             display help for command
$ GITHUB_REPOSITORY=octocat/HelloWorld GITHUB_REF=refs/heads/main npx @cdk-turnkey/stackname
OctocatHelloworldMain
$ GITHUB_REPOSITORY=octocat/HelloWorld GITHUB_REF=refs/heads/feature-branch-1 npx @cdk-turnkey/stackname --suffix webapp
OctocatHelloworldFeature-branch-1-webapp