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

aspublish

v0.1.6

Published

Minimalist publishing tool for GitHub and npm.

Downloads

65

Readme

aspublish

Minimalist publishing tool for GitHub and npm. Generates a changelog, makes a GitHub release of it, and publishes the package to npm.

Usage

Set GITHUB_TOKEN and NPM_TOKEN as environment variables.

To create a release on GitHub and publish the package to npm:

npx aspublish

May also obtain just the next version that will be created, if necessary:

npx aspublish --version

The returned version is empty if no release has been triggered.

Note that npm postversion etc. scripts will also run normally, and that the version number in package.json is irrelevant (may just be 0.0.0).

Commit format

Prefix either the commit subject or body:

Prefix | Release type | Pre 1.0.0 | Post 1.0.0 ------------|--------------|--------------------|--------------- breaking: | Major | 0.1.0 -> 0.2.0 | 1.0.0 -> 2.0.0 feat: | Minor | 0.1.0 -> 0.1.1 | 1.0.0 -> 1.1.0 fix: | Patch | 0.1.0 -> 0.1.1 | 1.0.0 -> 1.0.1

Except a few aliases and abbreviations, other prefixes will not trigger a new version / release.

Example

As a step during GitHub Actions:

- name: Make release
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    NPM_TOKEN:  ${{ secrets.NPM_TOKEN }}
  run: |
    VERSION=$(npx aspublish --version)
    if [ -z "$VERSION" ]; then
      echo "Changes do not trigger a release"
    else
      echo "Publishing new version: $VERSION"
      npx aspublish
    fi

Or, if obtaining the version upfront is not necessary:

- name: Make release
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    NPM_TOKEN:  ${{ secrets.NPM_TOKEN }}
  run: npx aspublish

See this repository's publish.yml for a complete configuration (replace node bin/aspublish.js with npx aspublish).