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

version-pong

v2.2.1

Published

Publish NPM package and automated bump version in the package.json based on Standard Version.

Downloads

6

Readme

Version-Pong

Publish npm package and automated bump version in the package.json based on Standard Version.

Version Pong Abilities

4 Steps will be performed in 1 Command!

  1. Update Peer Dependencies versions
  2. Tagging Version and Generate Auto Changelog
  3. Publish to npm registry
  4. Push all release change to target branch

Installation

As Global CLI

$ yarn global add version-pong

Local Project

$ yarn add -D version-pong

In package.json

{
    "scripts": {
        "release": "version-pong"
    },
    "version-pong": {
      "method": "yarn build && yarn publish"
    }
}

Settings

  • method - The method that perform for publishing library

What is watchDependencies?

If your package need to define peerDependencies, add target peer dependency package name to watchDependencies

add library name to watchDependencies.

example

In package.json

{
    "devDependencies": {
      "jest": "^26.0.1",
    },
    "watchDependencies": ["jest"]
}

Once version-pong is run with published command, it automatically generates peerDependencies.

example

In package.json

{
    "devDependencies": {
      "jest": "^26.0.1",
    },
    "watchDependencies": ["jest"],
    "peerDependencies": {
      "jest": ">=26.0.1",
    }
}

Settings

  • watchDependencies - List of devDependencies to be convert to peerDependencies.
  • peerDependencies - Auto Generated Dependencies in >=xx.xx.xx version format with watchDependencies by version-pong.

Usage

Publish Library

$ version-pong <tag>

example

$ version-pong minor

Publish with git tagPrefix

$ version-pong <tag> -t <tagPrefix>

example

$ version-pong minor -t eslint

Tag

Production Release (Master Branch Only)

  • Major - Breaking Change Release
  • Minor - Non-Breaking Change Release
  • Patch - Bug fix Release

Development Release (Dev Branch Only)

  • Beta - Development Release

Option

Contributors ✨