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

@instructure/conventional-changelog

v1.0.0

Published

Commitizen adapter following the conventional-changelog format.

Downloads

1,020

Readme

conventional-changelog

Provides prompt configuration for commitizen. The following questions are asked:

  1. Select the type of change that you're committing
    • Simply select the type from the provided list of options. Selecting feat will cause a minor version bump and selecting fix will cause a bugfix version bump. Marking your change as "breaking" (explained below) will cause a major version bump.
  2. Denote the scope of this change
    • This is a freeform input that allows you to specify one or more "scopes". This scope is used for grouping together like changes in the CHANGELOG. It's best to make this as specific as possible, and some great candidates are:
      • A specific component name (i.e. GradingHeader, Autocomplete, etc)
      • A specific section of the project (i.e. store, documentation, dependencies, etc)
      In the future, we may lint against a specific set of scope names.
  3. Write a short, imperative tense description of the change
    • This is the subject of your commit and should be kept to 72 characters or less
  4. List any issues closed by this change
    • List your JIRA tickets here. Whatever you type will be prefixed with "fixes", so entering "QUIZ-123" will result in "fixes QUIZ-123". You should ammend your commit message if you need to use a resolution type other than "fixes".
  5. Provide a test plan
    • List out your test plan steps. Whatever you type will be prefixed with "Test plan:\n".
  6. Is this a breaking change?
    • If this change is not backwards compatible to any potential consumer, then you should answer yes here. Answering yes here will cause a major version bump. 7a. Provide any important details about the breaking change
    • This question is only asked if you said yes when asked if the change is a breaking change. You should include details about why this is a breaking change, what the change impacts, and how consumers can mitigate it. 7b. (Optional) Provide any additional information you think might be useful
    • This question is only asked if you said no when asked if the change is a breaking change. Additional in-depth details that might be useful. This section is optional if the previously provided short description is simple enough.