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

@kuhe-org/publish-why-dont-we

v3.11.0

Published

conditionally publish/tag but do not consider a pre-existing version/tag as an exception

Downloads

73

Readme

node-publish-why-dont-we

npm install @kuhe-org/publish-why-dont-we

npx publish-why-dont-we or run main.js.

The script will do the following:

1

Find a prospective version. If the flag --use-latest-local-tag is used, then the latest local tag will be taken as the prospective version (unless the package.json version is higher)

In all other cases, the package.json version will be used as the prospective version.

2

Using this prospective version, the program will push a tag for this version only if it does not already exist on the remote.

It will also npm publish this version if and only if it does not already exist.

Existence of either a tag or npm version equal to the prospective version is not treated as a failure and instead ignored.

Notes

The suggested and designed use-case is running this command after automation has verified and merged a PR that may or may not bump the package.json version of a module.