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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@diogozx-org/commitlint-config

v1.0.1

Published

A shared Commitlint configuration for my projects

Downloads

65

Readme

Commitlint Config

A reusable Commitlint configuration for projects that follow Conventional Commits.

Requirements

  • Node.js 18 or newer
  • npm or Yarn
  • Commitlint CLI installed in the consuming project

Install

Install this package in your project:

npm install --save-dev @diogozx-org/commitlint-config @commitlint/cli

Or with Yarn:

yarn add --dev @diogozx-org/commitlint-config @commitlint/cli

Configure

Create commitlint.config.cjs in the root of your project:

module.exports = {
  extends: ['@diogozx-org/commitlint-config'],
};

The .cjs extension makes the CommonJS module format explicit, regardless of your project's package.json module type.

Rules

This config uses Conventional Commits and enforces:

  • A maximum header length of 100 characters
  • Lowercase commit types from this list: build, chore, ci, docs, feat, fix, perf, refactor, revert, style, and test
  • A non-empty subject without a trailing period
  • Body and footer lines no longer than 100 characters, with a blank line before each section

Example:

feat: add juror search

Add a searchable list of jurors to the trial workspace.

Optional: Commitizen

This repository also uses Commitizen for composing commits. Commitizen is a commit-writing helper, not a requirement for using this Commitlint configuration. Install and configure it separately if you want interactive commit prompts.

Development

yarn install --frozen-lockfile
yarn test
``

## License

MIT