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

@rainstormy/updraft

v1.1.0

Published

Updraft updates changelogs and bumps version numbers when you are about to release a new version of your project.

Downloads

57

Readme

Updraft – Release Automation

Updraft prepares a repository for an upcoming release by updating changelogs and bumping version numbers in package.json files.

It saves the changes to the files, but it does not make any Git commits or GitHub releases. You can automate these things in your CI/CD pipeline or do them manually after running the Updraft tool.

Supported file formats:

  • Markdown CHANGELOG.md and AsciiDoc CHANGELOG.adoc in Keep a Changelog format.
  • package.json files.

Command-Line Tool

Installation

npm install --save-dev --save-exact @rainstormy/updraft

or

pnpm install --save-dev --save-exact @rainstormy/updraft

or

yarn add --dev --exact @rainstormy/updraft

Usage

updraft [options]

Examples:

updraft --files 'CHANGELOG.md' 'package.json' --release-version '1.1.0'
updraft \
  --files 'package.json' 'packages/**/package.json' \
  --release-files 'CHANGELOG.md' \
  --check-sequential-release \
  --release-version '2.0.0-beta.1'

Options

--check-sequential-release

Verify that --release-version specifies a valid increment from the latest version detected in each file to be updated.

--files <pattern-1> <pattern-2> <pattern-3>...

Update the files matching the specified glob patterns whenever --release-version is specified.

--prerelease-files <pattern-1> <pattern-2> <pattern-3>...

Update the files matching the specified glob patterns only when --release-version has a -prerelease or +buildinfo segment.

--release-files <pattern-1> <pattern-2> <pattern-3>...

Update the files matching the specified glob patterns only when --release-version does not have a -prerelease or +buildinfo segment.

--release-version <major.minor.patch[-prerelease][+buildinfo]>

The semantic version number (SemVer) of the next release. The -prerelease and +buildinfo segments are optional. It accepts any input containing a substring that is a semantic version number, e.g. v2.0.0 or release/1.5.0-rc.0.