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

release-me

v1.4.2

Published

Replacement for `npm version` with automatic CHANGELOG generation

Downloads

19

Readme

Release Me

travis build CircleCI codecov coverage npm npm Greenkeeper badge

stop using npm version, use release-me

Automatic versioning and CHANGELOG generation.

How it works:

  1. when you're ready to release to npm:
  2. git checkout master; git pull origin master
  3. run release-me
  4. git push --follow-tags origin master; npm publish

release-me does the following:

  1. bumps the version in package.json/bower.json (based on your commit history)
  2. uses conventional-changelog (with conventional-changelog-release-me preset) to update CHANGELOG.md
  3. commits package.json (et al.) and CHANGELOG.md
  4. tags a new release

###Installation

As npm run script

Install and add to devDependencies:

npm i --save-dev release-me

Add an npm run script to your package.json:

{
  "scripts": {
    "release": "release-me"
  }
}

Now you can use npm run release in place of npm version.

This has the benefit of making your repo/package more portable, so that other developers can cut releases without having to globally install release-me their machine.

As global bin

Install globally (add to your PATH):

npm i -g release-me

Now you can use release-me in place of npm version.

This has the benefit of allowing you to use release-me on any repo/package without adding a dev dependency to each one.