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

not-prerelease

v1.0.1

Published

Detect if the current package version, or the passed version is a prerelease

Downloads

2,027

Readme

not-prerelease

Detect if the current npm version call is a prerelease or not. That way the version lifecycle script can do things selectively in actual releases vs prereleases, such as update a changelog with conventional-changelog

Installation

$ npm install --save-dev not-prerelease

Then edit your package.json to have:

  "scripts": {
    "version": "not-prerelease && thing-i-dont-want-to-do-on-prerelease || is-prerelease"
  }

Now when you run:

$ npm version <major|minor|patch|prerelease>

Then thing-I-dont-want-on-prerelease won't be run during a prerelease but, will be run done during a major, minor, or patch releases.

Other information

This package exports two binaries both of which default to looking at the version of package.json in the current directory, but they can also be passed one argument, a version to check.

  • not-prerelease
    • If the version in package.json or that was passed is a prerelease it will exit 1 (failure) otherwise it will exit 0.
  • is-prerelease
    • If the version in package.json or that was passed is a prerelease it will exit 0 (success) otherwise it will exit 1.