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

@not-an-aardvark/node-release-script

v0.1.0

Published

Script for automatically generating releases

Downloads

56

Readme

node-release-script

An opinionated release script

Usage

$ npm install -g @not-an-aardvark/node-release-script
$ node-release-script

What does it do?

Note that this tool is very opinionated, is not intended to be a general-purpose release tool. If you're looking for that, consider using semantic-release instead.

This tool does the following:

  • Generates a changelog from the git commits since last release
  • Updates the version number in package.json, according to semantic versioning
  • Creates a git commit for the release
  • Creates a git tag for the release

Note that this does not push the updates anywhere. You should run npm publish, git push, and git push --tag afterwards to update the remotes.

The updated version number is determined based on the commit messages since the last release. Your commit messages should start one of the following prefixes:

  • Breaking: semver-major
  • New: semver-minor
  • Update: semver-minor
  • Fix: semver-patch
  • Docs: semver-patch
  • Build: semver-patch
  • Upgrade: semver-patch
  • Chore: semver-patch

The changelog will include links to issues and commits, based on the origin remote URL in your local git repository. To ensure that the links in the changelog work, make sure your remote is called origin, it uses the https: protocol, and it is linked to an existing reporitory on GitHub.

In order for commits to be added correctly, the changelog must be in a file called CHANGELOG.md in the project root. It must start with the text # Changelog followed by two linebreaks.

License

MIT