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

@eddlondon/commitlint-config

v1.2.1

Published

Our default export contains rules related to commits by following conventional commits specifications

Downloads

2

Readme

EDD Commitlint Config

Our default export contains rules related to commits by following conventional commits specifications.

Prerequisites

npm install npm@latest -g

npm install --global yarn

Installation

install commitlint

npm install --save-dev @commitlint/{cli,config-conventional}

yarn add @commitlint/{cli,config-conventional} -D

Install husky

npm install husky --save-dev

yarn add husky --dev

activate hooks

npx husky install

yarn husky install

Add hook

npx husky add .husky/commit-msg "npx --no -- commitlint --edit ${1}"

Hooks not running

  • Ensure that you don't have a typo in your filename. For example, precommit or pre-commit.sh are invalid names. See Git hooks documentation for valid names.
  • Check that git config core.hooksPath returns .husky (or your custom hooks directory).
  • Verify that hook files are executable. This is automatically set when using husky add command but you can run chmod +x .husky/<hookname> to fix that.
  • Check that your version of Git is greater than 2.9.

Usage

  • create a file called .commitlintrc.json in root directory of application where .git file is located.
  • paste the following snippet {   extends: ['@eddlondon'];}.

Publish

run the following command

yarn push-patch

npm run push-minor

yarn push-minor

npm publish access=public