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

@jbahr/semantic-release-testing

v5.1.0

Published

sr testing

Readme

semantic-release-testing

sr testing

semantic-release release branches set up

  • update @semantic-release/git and semantic-release to use @beta versions
  • yarn add -D @semantic-release plugins
  • update release: {} to package.json to add semantic-release configuration (use this repo as a guide)
  • create local 'beta' branch
  • git push beta branch to remote repo

semantic-release branches workflow

  • Non breaking changes are released on 'master' branch
  • Breaking changes are released on 'beta' branch
    • 'Beta' branch needs to be updated to match 'master' branch eg: in local beta branch: git merge master
    • Create new working branch off of 'beta' branch
    • yarn commit - be sure to add clear details on how to fix breaking changes when prompted to include 'breaking changes description'
    • git push, merge into 'beta' branch
  • Continue adding non-breaking changes to 'master' branch
  • Once breaking changes are fixed
    • git pull 'master' and 'beta' branches
    • Merge 'beta' branch into 'master' branch
    • If merge conflicts 'Accept current change'
    • git push, merge into 'master'