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

is-unpublished

v0.3.4

Published

Determine if the current version of a package is unpublished

Downloads

2

Readme

Build Version License

A scripting tool for CI environments to determine if your package needs to be published.

npm install -g is-unpublished

if is-unpublished; then
  # Do whatever you need to do to publish your package!
fi

This tool supports the following package formats:

Binary releases

If you don't have the ability to install NPM packages in your environment, you can install a binary release.

$ curl -L https://github.com/rzane/is-unpublished/releases/download/v0.3.3/is-unpublished-`uname -s`-`uname -m` > is-unpublished
$ chmod +x is-unpublished
$ ./is-unpublished --version
0.3.3

Github Action

You can also use this package as a Github action. The action version coincides with the published NPM package version.

Inputs

cwd

The directory your package lives in.

Outputs

name

The name of your package.

version

The current version of your package.

is-unpublished

Indicates that your package hasn't been published yet.

Example usage

Publish to NPM

Make sure to set NPM_TOKEN in your repo settings.

- name: Setup Node
  uses: actions/setup-node@v1
  with:
    node-version: 12
    registry-url: https://registry.npmjs.org

- name: Check
  id: check
  uses: rzane/[email protected]

- name: Publish
  run: yarn install && yarn publish --access public
  if: ${{ steps.check.outputs.is-unpublished == 'true' }}
  env:
    NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

- name: Release
  uses: actions/create-release@v1
  if: ${{ steps.check.outputs.is-unpublished == 'true' }}
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
  with:
    tag_name: v${{ steps.check.outputs.version }}
    release_name: v${{ steps.check.outputs.version }}

Publish to RubyGems

Make sure to set RUBYGEMS_TOKEN in your repo settings.

- name: Setup Ruby
  uses: actions/setup-ruby@v1
  with:
    ruby-version: 2.6.x
    registry-url: https://registry.npmjs.org

- name: Check
  id: check
  uses: rzane/[email protected]

- name: Publish
  if: ${{ steps.check.outputs.is-unpublished == 'true' }}
  run: |
    mkdir -p $HOME/.gem
    touch $HOME/.gem/credentials
    chmod 0600 $HOME/.gem/credentials
    printf -- "---\n:rubygems_api_key: ${RUBYGEMS_TOKEN}\n" > $HOME/.gem/credentials
    gem build *.gemspec
    gem push *.gem
  env:
    RUBYGEMS_TOKEN: ${{ secrets.RUBYGEMS_TOKEN }}

- name: Release
  if: ${{ steps.check.outputs.is-unpublished == 'true' }}
  uses: actions/create-release@v1
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
  with:
    tag_name: v${{ steps.check.outputs.version }}
    release_name: v${{ steps.check.outputs.version }}