JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 138
  • Score
    100M100P100Q92497F
  • License MIT

Automates the full release process for npm packages

Package Exports

  • npm-github-release

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (npm-github-release) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

npm-github-release NPM Package

Automate the full release process for npm packages.

When publishing npm packages, there is more to do than just running npm package. Usually, you end up doing the following steps:

  • Versioning
  • Creating a release on GitHub with release notes
  • Publishing to npm

npm-github-release automates these steps in a simple way. Simply run npm run release, specify the release type (major, minor, patch), provide release notes and you are done. After npm-github-release finishes, you will have a new version of your package available on npm as well as a corresponding release on GitHub with release notes.

Only macOS and Linux are supported.

Usage

  1. Install npm-github-release
npm i --save-dev npm-github-release
  1. Add a new release script to your package.json file
"scripts": {
  "release": "npm-github-release"
}
  1. Run npm run release.

Demo

Demo

Settings

A GitHub Personal access token will be needed to create the release on GitHub. Adding this token to an environment variable named GITHUB_API_TOKEN is recommended as this will allow npm-github-release to skip prompting for it.