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

@anylint/commitlint-config

v1.0.7

Published

Shareable Commitlint config enforcing conventional commit with workspace scopes support

Downloads

1

Readme

AnyLint Logo

@anylint/commitlint-config

@anylint/commitlint-config is a configuration package for Commitlint designed to enforce consistent and conventional commit messages within your projects. This standardization makes it easier to track and manage changes in your codebase.

Features 🚀

  • Conventional Commit Messages: Promotes the use of conventional commit message formats, such as Conventional Commits, to enhance codebase manageability.

  • Workspace Scopes: Offers support for monorepo setups by enabling you to specify workspace scopes in commit messages.

Installation

To install, run the following command:

npm install @anylint/commitlint-config @commitlint/cli --save-dev

Prompts

To prompts install, run the following command:

npm install @commitlint/prompt-cli --save-dev

Add commit script to your package.json:

{
  "scripts": {
    "commit": "commit"
  }
}

Run npm run commit to commit your changes.

Commit Message Format

The commit message format enforced by this configuration is based on the Conventional Commits specification. This specification defines a set of rules for creating commit messages that are easy to read and parse by both humans and machines.

The following is an example of a commit message that follows the Conventional Commits specification:

feat(core): add new feature

Configuration

Monolithic Repository

Edit commitlint.config.js:

module.exports = {
  extends: ['@anylint/commitlint-config'],
  rules: {
    // Add additional rules here.
  },
}

Monorepo Repository

Edit commitlint.config.js:

module.exports = {
  extends: ['@anylint/commitlint-config', '@anylint/commitlint-config/workspace-scopes'],
  rules: {
    // Add additional rules here.
  },
}

Workspace scopes are automatically inferred from the workspaces property in your package.json file and added to the scopes property in your commitlint.config.js file. For example, if your package.json file contains the following:

{
  "workspaces": ["packages/core", "packages/ui"]
}

Then you should use core and ui as scopes in your commit messages:

$ git commit -m "feat(core): add new feature"

Additionally, you can use workspace as a scope to indicate that your commit message applies to the entire monorepo:

$ git commit -m "feat(workspace): add new feature for all packages"