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

@hellolitebox/commitlint

v1.1.3

Published

Lint your commits, the litebox-way

Downloads

468

Readme

Lint your commits, litebox-way

hellolitebox/commitlint

Shareable commitlint config enforcing Litebox convention :)

Getting started

Run this commands inside the root of your project:

yarn add -D @hellolitebox/commitlint @commitlint/cli @hellolitebox/commit-prompt commitizen
echo "const config = require('@hellolitebox/commitlint');
module.exports = config({ taskIdPrefixes: [] });" > commitlint.config.js
npx husky add .husky/commit-msg  'npx --no -- commitlint --edit ${1}'

Add this to your package.json

  "config": {
    "commitizen": {
      "path": "@hellolitebox/commit-prompt"
    }
  },
  "scripts": {
    "commit": "git-cz"
  }

Config taskIdPrefixes

If you want that every commit has always a task id in the subject, you can add it as a string inside the taskIdPrefixes array in the commitlint.config.js file, e.g:

module.exports = config({ taskIdPrefixes: ['CU-'] });

This way, to be considered a valid commit, the message should be:

feat: CU-1234 add something

If you add more taskIdPrefixes to the array, any of those will be considered valid, e.g:

module.exports = config({ taskIdPrefixes: ['CU-', 'HOTFIX'] });

feat: HOTFIX add something

The above commit message is also valid.

Make a commit

git add .

yarn commit

After run yarn commit, an interactive screen will appear, letting you fill all the commit parts, one by one.

The required ones are: scope and subject, the others can be skipped normally.