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

conventional-recommended-workflow

v1.0.0

Published

apply the recommended workflow outlined in conventional-changelog-cli.

Downloads

15

Readme

Conventional Recommended Workflow

Build Status NPM version

Automatic CHANGELOG.md generation, using GitHub's new squash button and the workflow outlined in conventional-changelog-cli.

how it works:

  1. when you land commits on your master branch, select the Squash and Merge option.
  2. add a title and body that follows the conventional-changelog conventions.
  3. when you're ready to release to npm:
  4. checkout master.
  5. run conventional-recommended-workflow.
  6. git push --tags; git push origin master; npm publish.

conventional-recommended-workflow does the following:

  1. bumps the version in package.json
  2. runs conventional-changelog and updates CHANGELOG.md.
  3. commits package.json and CHANGELOG.md.
  4. tags a new release.

Initial CHANGELOG.md Generation

When you're generating your changelog for the first time, simply do:

conventional-recommended-workflow --first-release

Installation

npm i conventional-recommended-workflow

Automating

Add this to your package.json

{
  "scripts": {
    "release": "conventional-recommended-workflow"
  }
}

License

ISC