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

@mediamonks/commitlint-config

v1.0.2

Published

Sharable commitlint config based on Media.Monks Frontend Coding Standards

Downloads

2,321

Readme

@mediamonks/commitlint-config

Set some basic conventions and rules for our commit messages using commitlint.

Note that we have not enabled the type and scope rules that are "conventional", because we don't use them. It just focuses on the basics outlined in this article on how to write good commit messages.

Installation

Install @commitlint/cli and @mediamonks/commitlint-config

npm i -D @commitlint/cli @mediamonks/commitlint-config

Create your configuration

This can be added in a lot of places (see docs), but we recommend the package.json.

{
  ...
  "commitlint": {
    "extends": ["@mediamonks/commitlint-config"]
  }
}

Set up husky

To make sure that your commit messages are validated when you are committing.

# Install Husky v6
npm i -D husky

# Activate hooks
npx husky install

# Add hook
npx husky add .husky/commit-msg  'npx --no -- commitlint --edit ${1}'

Rules

Errors

  • Subject line must be 72 characters max
  • Subject line must start with a capital letter
  • Subject line must not end with a period
  • There must be an empty line between the subject and the body
  • Body must be 72 characters max per line

Warnings

  • Subject line must be 30 characters min