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

create-action-llama

v0.1.5

Published

Create a new Action Llama project

Readme

create-action-llama

Scaffold a new Action Llama project.

Usage

npx create-action-llama my-app

Development

Prerequisites

  • Node.js >= 18
  • npm

Install dependencies

npm install

Versioning & Publishing

This project uses Changesets for version management and npm publishing.

Adding a changeset

When you make a change that should be released, create a changeset:

npx changeset

You'll be prompted to:

  1. Select the package (this one)
  2. Choose the semver bump type (patch, minor, or major)
  3. Write a summary of the change

This creates a markdown file in .changeset/ describing the change. Commit it with your PR.

Releasing a new version

When you're ready to release:

# 1. Consume all pending changesets and bump the version in package.json
npx changeset version

# 2. Review the updated package.json version and CHANGELOG.md
git add -A && git commit -m "chore: release"

# 3. Publish to npm
npm publish --access public

# 4. Push the release commit and tag
git push && git push --tags

CI Publishing (GitHub Actions)

For automated releases, add the Changesets GitHub Action to your workflow:

# .github/workflows/release.yml
name: Release

on:
  push:
    branches: [main]

permissions:
  contents: write
  pull-requests: write

jobs:
  release:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
          registry-url: "https://registry.npmjs.org"
      - run: npm install
      - uses: changesets/action@v1
        with:
          publish: npm run release
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

Set NPM_TOKEN in your repository secrets (Settings > Secrets > Actions) with an npm access token that has publish permissions.

License

MIT