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

boomper-github-app

v1.1.0

Published

A GitHub app that bumps version numbers in files whenever new releases are published to GitHub

Downloads

7

Readme



NPM package

Usage

Firstly, you’ll need to install the Boomper GitHub App. This listens out for any releases, or any changes to the configuration.

Then, add a .github/boomper.yml configuration file to the GitHub repository where you publish new releases to.

For example, given the following .github/boomper.yml file:

updates:
- path: README.md
  pattern: 'https://someurl.com/(v.*)/download.zip'

And given the following README.md file:

Install with `curl https://someurl.com/v1.0.0/download.zip`

Then when a new release is published (e.g. v2.0.0), Boomper will update the README.md to:

Install with `curl https://someurl.com/v2.0.0/download.zip`

Examples

Buildkite Plugin Readmes

updates:
- path: README.md
  pattern: 'my-org/my-plugin#(v.*):'

Configuration options

You can configure Boomper using the following key in your .github/boomper.yml file:

|Key|Required|Description| |-|-|-| |updates|Required|A list of paths and patterns to update when a new release is published.| |updates.[].path|Required|The path to the file to update.| |updates.[].pattern|Required|The regular expression containing a single group, which will be used to match and update the version number in the file.| |updates.[].branch|Optional|The branch to update. Default is the repository's default branch (e.g. master).| |branches|Optional|The branches to listen for configuration updates to .github/boomper.yml. Useful if you want to test the app on a pull request branch. Default is "master".|

Boomper also supports Probot Config, if you want to store your configuration files in a central repository.

Developing

If you have Node v10+ installed locally, you can run the tests, and a local app, using the following commands:

# Install dependencies
yarn

# Run the tests
npm test

# Run the app locally
npm start

If you don't have Node installed, you can use Docker Compose:

# Run the tests
docker-compose run --rm app npm test

Contributing

Third-pary contributions are welcome! 🙏🏼 See CONTRIBUTING.md for step-by-step instructions.

If you need help or have a question, let me know via a GitHub issue.

Deployment

If you want to deploy your own copy of Boomper, follow the Probot Deployment Guide.

Releasing

Run the following command:

git checkout master && git pull && npm version [major | minor | patch]

The command does the following:

  • Ensures you’re on master and don't have local, un-commited changes
  • Bumps the version number in package.json based on major, minor or patch
  • Runs the postversion npm script in package.json, which:
    • Pushes the tag to GitHub
    • Publishes the npm release
    • Opens the GitHub releases page so you can publish the release notes