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-changelog-weaveability

v1.1.0

Published

A custom preset for conventional changelog and semantic release

Downloads

7

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

weaveability-userweaveability-user

Keywords

Readme

Conventional Changelog Weaveabilty

A custom preset for conventional changelog and semantic release

Installing

npm install --save-dev conventional-changelog-weaveability

Additional Setup

Release rules will need to be provided for each type and provided to the commit-analyzer

Docs

Commit Message Format

A commit message currently consists of:

  • header (mandatory): consisting of a type and subject
  • body (optional)
  • footer (optional)
    <type><subject>
    <BLANK LINE>
    <body>
    <BLANK LINE>
    <footer>

Type

The type must prefix your commit message inorder to be detected and used by the commit-analyser and notes-writer

Valid types

  • [FEATURE] - When new functionality has been added to the application
  • [FIX] - For general bug fixes
  • [REFACTOR] - Changeing the implementation of existing functionality
  • [STYLE] - For any changes/fixes to existing styleing
  • [MERGE] - For merge related actions (e.g "resolving conflicts" or "fixing failed merge requests")
  • [CI] - For work relating to Continuious Integration
  • [TEST] - For adding/fixing/refactoring Tests
  • [DOC] - For adding/changing documentation

Subject

The subject should contain a breif precice description of the change

Body

The body should include the motivation for the change and contrast this with previous behavior.

Footer

The footer is for additional information like whether the Merge is a breaking change and/or the jira ticket ID

  • Breaking Changes: Add BREAKING CHANGE or BREAKING CHANGES followed by a description of the breaking change
  • Referencing a ticket: #TICKET-1234

Revert

If the commit reverts a previous commit, it should begin with revert: , followed by the header of the reverted commit. In the body it should say: This reverts commit <hash>.