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

versioning-tool

v2018.10.8-11

Published

CLI tool for updating npm package version and tagging git repos for release.

Downloads

10

Readme

versioning-tool

CLI tool for updating npm package version and tagging git repos for release.

oclif Version Build Status Open Issues Downloads/week License

Usage

$ npm install -g versioning-tool
$ vt COMMAND
running command...
$ vt (-v|--version|version)
versioning-tool/2018.10.8-9 darwin-x64 node-v10.1.0
$ vt --help [COMMAND]
USAGE
  $ vt COMMAND
...

Version Formatting

You can specify the date format that will be used by adding the following section to your package.json file:

"versioning": {
  "date-format": "yyyy.mm.dd"
}

Commands

vt current

Displays current version

USAGE
  $ vt current

OPTIONS
  -h, --help  show CLI help

See code: src/commands/current.ts

vt help [COMMAND]

display help for vt

USAGE
  $ vt help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

vt update

Adds a git tag for next version and update package.json to match.

USAGE
  $ vt update

OPTIONS
  -f, --format=format    Format that the date portion should be in
  -h, --help             show CLI help
  -m, --message=message  The message you want attached to the git tag
  -p, --push             Run a git push and git push --tags after updating the version
  -v, --version=version  Force a new version number

See code: src/commands/update.ts