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

@nrfcloud/github-release-util

v3.0.3

Published

Automates creating a github releases and uploading build assets.

Downloads

21

Readme

@nrfcloud/github-release-util

Utility script to automate gitHub release workflow and uploading of build assets (optional).

Usage

Interactive Mode

To use with your project install (npm i -D @nrfcloud/github-release-util) and add the following to your package.json. Afterwards, you can run npm run release to automatically create a new release on GitHub.

{
    "scripts": {
        "release": "gru"
    }
}

CLI mode

By default this script walks the user through the decisions to create a release. It also has an option to send in all the options at once (no prompt). The following is an example of the available options. You can get this output by running npx gru --cli --help.

Usage: index.ts [options]

Options:
  -o, --owner <owner>                     owner (default to .env file)
  -r, --repo <repo>                       repo (default to .env file)
  -k, --git-hub-token <gitHubToken>       gitHub token (default to .env file)
  -n, --release-name <releaseName>        release name (default to tag)
  -m, --release-message <releaseMessage>  release message
  -t, --target-tag <targetTag>            release tag
  -p, --prev-tag <prevTag>                previous tag (for commit message purposes, only used if release message is not defined)
  -b, --is-beta                           Is beta release
  -c, --should-upload-build-assets        compress and upload build assets
  -d, --build-dir <buildDir>              build dir
  -l, --cli                               cli
  -v, --show-token                        show token (shows token in output, defaults to false.)
  -h, --help                              output usage information

# without build assets
npx gru --cli -t "<tag>"

# with build assets
npx gru --cli -t "<tag>" -c -d "<build dir>"

# this can also be called without the alias by using the following:
npx @nrfcloud/github-release-util --cli -t "<tag>" -c -d "<build dir>"

Configuration

This script automatically looks for a .env file at the project root. The repo includes a .env.sample file. To use with your project, run cp node_modules/@nrfcloud/github-release-util/.env.sample ./.env. The file includes the following config variables:

GITHUB_REPO=
GITHUB_OWNER=
GITHUB_TOKEN=

In interactive mode, you will be prompted for these if the values don't exist in the .env file.

In CLI mode, the script will fall back to the values in the .env file if not passed in explicitly.

Get a GitHub token by following these steps.

Gotchas

The release must be linked to a tag. And the tag for which you're deploying must have been created before you run this script.