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

@nesvel/commitlint-config

v1.0.3

Published

Shared commitlint configuration for enterprise NestJS monorepos with Conventional Commits and Commitizen support

Readme

@nesvel/commitlint-config

Shared commitlint configuration for the Nesvel monorepo. Enforces Conventional Commits specification.

Installation

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

Usage

Create commitlint.config.js in your project root:

export default {
  extends: ['@nesvel/commitlint-config'],
};

Or in commitlint.config.json:

{
  "extends": ["@nesvel/commitlint-config"]
}

Commit Message Format

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

[optional body]

[optional footer]

Types

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation changes
  • style: Code style changes (formatting, semicolons, etc.)
  • refactor: Code refactoring (no feat/fix)
  • perf: Performance improvements
  • test: Adding or updating tests
  • build: Build system or dependency changes
  • ci: CI/CD configuration changes
  • chore: Maintenance tasks
  • revert: Revert previous commit
  • release: Release commits

Scopes

  • api: API application
  • admin: Admin application
  • shared: Shared packages
  • tools: Tool packages (eslint, jest, etc.)
  • config: Configuration changes
  • deps: Dependency updates
  • monorepo: Monorepo-wide changes
  • release: Release-related changes

Examples

feat(api): add user authentication endpoint
fix(admin): resolve dashboard loading issue
docs(readme): update installation instructions
chore(deps): upgrade nestjs to v10
refactor(shared): simplify error handling logic
test(api): add unit tests for auth service
ci(github): update workflow to use pnpm
perf(api): optimize database queries

Rules

  • Header max length: 100 characters
  • Subject must be lowercase
  • Subject must not end with a period
  • Type and scope must be lowercase
  • Type is required
  • Scope is required (for better monorepo organization)