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 🙏

© 2024 – Pkg Stats / Ryan Hefner

prerelease-checks

v1.0.0

Published

Run essential pre-release checks before releasing an npm package

Downloads

18

Readme

prerelease-checks

Run essential pre-release checks before releasing an npm package.

💞 Works well with standard-version!

If you like this project, please star it & follow me to see what other cool projects I'm working on! ❤️

🙋‍♂️ Why?

Because there are many points of failure when making a release.

This CLI runs a thorough check to guarantee a successful package release:

npm

  • ✅ Assert npm version
  • ✅ Validate package.json
    • ✅ Check valid npm name
    • ✅ Check valid semver version
    • ✅ Verify public package
  • ✅ Verify npm registry is reachable (in case custom)
  • ✅ Verify npm publish registry is reachable
  • ✅ Verify user is authenticated to publish registry and has permissions

Git

  • ✅ Assert Git version
  • ✅ Verify working directory is clean
  • ✅ Verify current branch is release branch
  • ✅ Verify remote head exists
  • ✅ Verify current branch is identical to upstream

🚀 Install

npm i -D prerelease-checks

npx

You can also install-and-run as you need it via npx:

npx prerelease-checks

🚦 Quick Setup

As a prepublish hook

Add prerelease-checks as a prepublishOnly hook in your package.json:

 {
   "scripts": {
+    "prepublishOnly": "prerelease-checks"
   }
 }

With standard-version

If you're using standard-version, add it to their prerelease hook.

 {
   "scripts": {
+    "prerelease": "prerelease-checks",
     "release": "standard-version"
   }
 }

Other

You can prepend your release script with prerelease-checks.

 {
   "scripts": {
+    "release": "prerelease-checks && my-custom-release-command",
   }
 }

🙏 Credits

Many inspirations taken from the prerequisite checks from np.