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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@deepracticex/commitlint-config

v0.0.1

Published

Shared commitlint configuration for Deepractice projects

Downloads

5

Readme

@deepracticex/commitlint-config

Shared commitlint configuration for Deepractice projects following Conventional Commits.

Installation

pnpm add -D @deepracticex/commitlint-config @commitlint/cli

Usage

Create commitlint.config.js in your project root:

export default {
  extends: ["@deepracticex/commitlint-config"],
};

Commit Message Format

<type>(<scope>): <subject>

<body>

<footer>

Type

Must be one of:

  • feat - New feature
  • fix - Bug fix
  • docs - Documentation changes
  • style - Code style changes (formatting, missing semicolons, etc)
  • refactor - Code refactoring (neither fixes a bug nor adds a feature)
  • perf - Performance improvements
  • test - Adding or updating tests
  • build - Build system or external dependencies (webpack, npm, etc)
  • ci - CI/CD changes (GitHub Actions, etc)
  • chore - Other changes that don't modify src or test files
  • revert - Revert a previous commit

Scope (Optional)

The scope should be the name of the package or area affected:

  • error-handling
  • logger
  • eslint-config
  • typescript-config
  • etc.

Subject

  • Use imperative, present tense: "change" not "changed" nor "changes"
  • Don't capitalize first letter
  • No period (.) at the end
  • Max 100 characters

Body (Optional)

  • Use imperative, present tense
  • Include motivation for the change and contrast with previous behavior
  • Max 200 characters per line

Footer (Optional)

  • Reference issues: Fixes #123, Closes #456
  • Breaking changes: BREAKING CHANGE: <description>
  • Max 200 characters per line

Examples

Simple commit

feat: add user authentication

With scope

fix(logger): resolve file rotation issue

With body

refactor(error-handling): simplify error factory API

Remove redundant error creation methods and consolidate into a single
factory function for better maintainability.

With breaking change

feat(eslint-config): upgrade to ESLint 9

BREAKING CHANGE: Requires ESLint 9.0.0 or higher. Update your ESLint
dependency before upgrading this package.

With issue reference

fix(logger): prevent memory leak in file transport

Fixes #42

Integration with Lefthook

Add to your lefthook.yml:

commit-msg:
  commands:
    commitlint:
      run: npx commitlint --edit {1}

Integration with Changesets

Commitlint works seamlessly with changesets. After your commit passes validation, run:

pnpm changeset

Rules

This config extends @commitlint/config-conventional with the following customizations:

  • Subject case: Flexible (allows any case)
  • Subject max length: 100 characters
  • Body max line length: 200 characters
  • Footer max line length: 200 characters

License

MIT