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

commitlint-config-techor

v3.0.23

Published

Check your commits with Techor's commitlint config

Downloads

47

Readme

Getting Started

Skip if you have already run npm install techor:

npm install commitlint-config-techor -D

Configuration

Create a .commitlintrc.yml file in your project root and extend techor:

extends: techor

Set up Husky

Use Husky to register Git Hooks to automatically check whether it is legal before committing.

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

Check if the .husky is successfully generated in the project root:

+ └── .husky
+     ├─── _
+     └─── commit-msg

From now on, you just need to commit; the check happens after the commit. If everything is legal, there will be no prompts.

package.json

Pre-commit checks via Git Hook are only enabled when other team members clone the project and run npm install.

Save commit-check and husky install commands for teamwork and CI:

{
    "scripts": {
        "install": "husky install",
        "commit-check": "commitlint --from=HEAD~1 --verbose"
    }
}

pnpm run commit-check:

Continuous Integration

Typically, you double-check commits before publishing and on relevant workflows, using GitHub Actions as an example:

Create a workflow for commit check /.github/workflows/commit-check.yml:

name: Commit Check
on:
    push:
        branches:
            - '**'
    pull_request_target:
        types:
            - opened
            - reopened
            - edited
            - synchronize

jobs:
    check:
        timeout-minutes: 15
        runs-on: ubuntu-latest
        strategy:
            matrix:
                node-version: [20]
        steps:
            - uses: actions/checkout@v4
              with:
                  fetch-depth: 0
            - uses: actions/setup-node@v4
              with:
                  node-version: ${{ matrix.node-version }}
                  cache: 'npm'
            - run: npm ci
            - run: pnpm run commit-check

Commit Header Format

The header has a particular format that includes a Type, a Target, and a Summary:

Type(Target): Summary
  ┊     ┊
  ┊     └─⫸ Target: Workspace, Package or Role
  ┊
  └─⫸ Type: Bump, Feat, New, Perf, Add, Update, Improve, Fix, Deprecate, Drop, Docs, Upgrade, Revert, Example, Test, Refactor, Chore, Misc

For the full documentation, check out the Techor's conventional commits