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

@lazy-release/cli

v0.2.2

Published

A CLI tool that automates versioning, publishing, and changelog generation with full support for multi-package repositories.

Downloads

40

Readme

🚀 lazy-release

Contributors Welcome NPM Version GitHub License

Automates versioning, publishing, and creating changelogs for Node.js projects using conventional commits and supports multi-package repos.

✨ Features

  • 📝 Automated Changelogs - Generate nice looking changelogs from conventional commits
  • 🔖 Version Management - Automatic semantic versioning based on commit messages
  • 🏷️ Git Tag Management - Automatically creates and publishes git version tags
  • 📦 Package Manager Agnostic - Works with npm, pnpm, yarn, and bun
  • 🤖 GitHub Integration - Automatic PR creation and GitHub releases
  • 🧪 Snapshot Releases - Create preview versions for testing
  • 🎯 Monorepo Support - Manage multiple packages in a single repository

📚 Documentation

⚙️ Prerequisites

  1. Use squash merge for pull requests.

In your repo settings:

  • Go to Settings > General > Pull Requests
    • Uncheck "Allow merge commits"
    • Check "Allow squash merges"
      • Choose "Pull request title" for default commit message
  1. Update workflow permissions
  • Go to Settings > Actions > General
    • Set "Workflow permissions" to "Read and write permissions"
    • Check "Allow GitHub Actions to create and approve pull requests"

📖 Quick Start

[!NOTE]
It's recommended to run lazy-release in a CI/CD environment (like GitHub Actions) for automated and consistent release workflows.

  1. Install the CLI:
pnpm i @lazy-release/cli -D
  1. Add a script to your package.json:
{
  "scripts": {
    "lazy-release": "lazy-release"
  }
}
  1. Run the CLI:
pnpm lazy-release --npm-token $NPM_TOKEN --github-token $GITHUB_TOKEN --access public

🔄 Workflow

  1. A dev merges a Pull Request into the main branch using squash merge.

[!NOTE]
The PR should be prefixed with conventional commit prefix e.g "fix", "chore", "feat", etc...

  1. A Release PR gets created. release-pr

A Release PR....

  • Bumps the version in the package.json files
  • Updates the lock files
  • Creates or updates changelogs changelogs
  1. A release is created once the Release PR is merged. A release is...
  • Publishing packages to npm (If you provide a NPM_TOKEN and the package.json does not have "private": true)
  • Creates a GitHub release (If you provide a GITHUB_TOKEN) github-release

🌟 Projects Using lazy-release

[!NOTE]
If you are using lazy-release in your project, please consider adding it to this list by submitting a pull request!

💡 This tool was inspired by

  • Vue.js (Their nice changelogs)
  • Nuxt.js (Release PRs, use of emojis etc)