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

pkgver

v0.2.1

Published

CLI tool for semantic versioning

Downloads

3

Readme

pkgver

CLI tool for managing versions in Package files. (This includes package.json, bower.json, etc)

Description

Provides a simple CLI for reading, setting, bumping, and syncing the version numbers across various package files.

Example, you're writing a Javascript module that could be installed from either NPM or Bower. Consequently, you have a package.json and a bower.json in your module's directory. Using pkgver, you run pkv bump or pkv set 1.2.3, and both of these files are now updated and in sync!

Usage

pkgver can be invoked via pkgver, pkv, or ver from the command line.

Most methods look something like:

pkg <action> [part] [value] --options

Where part and value are optional, depending on the action.

The part option can be one of the 4 semver parts: Major.minor.patch-pre

Log

pkv [log] (pkv or pkv log)

Will log out the name & version of all Package files in the current directory. Will also mark any invalid version numbers.

Sync

pkv sync

Will sync the version numbers in all Package files in the current directory to the highest version number found.

Set

pkv set [part] <value> (pkv set 1.2.3 or pkv set patch 12)

Will set the version numbers in all Package files in the current directory to the given value.

If part is not given, value must be a valid semver version number.

If part is given (Major.minor.patch-pre), the value must be an integer (Except in the case of pre, in which any alpha-numeric value is valid).

Bump

pkv bump [part] (pkv bump or pkv bump pre)

Will bump the version numbers in all Package files in the current directory.

If part is given (Major.minor.patch-pre), then the requested piece will be bumped by 1.

If part is not given, pkgver will default to bumping the patch number by 1.

Note: if pre is bumped, and no pre number currently exists, the patch number will be bumped by 1, and pre will be set to 1. (1.0.0 -> 1.0.1-1)

Note: if patch is bumped, and a pre number currently exists, the patch number will NOT change, but the pre will be dropped. (1.0.1-3 -> 1.0.1)