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

simple-commitlint

v0.0.4

Published

a simple commitlint

Downloads

2

Readme

GitHub package.json version

simple-commitlint

commitlint, but in simpler ✨

how to use

  1. npm i -D simple-commitlint / yarn -D simple-commitlint
  2. create a config file simple-commitlintrc with one of the following extensions: js, ts, mjs, json, yml/yaml

plain configuration

(taken from types.ts, for further details check it out)

interface Config {
  /**
   * prepare the commit by providing an own logic to separate title and body (return a string if it's an invalid commit to prepare)
   * by default it's title = row[0], body = otherRows
   */
  prepareCommit?: (raw: string) => Pick<Commit, 'title' | 'body'> | string;
  /** an array of rules (which must have a name and a validation), if left empty the linter exits with code 0 */
  rules?: Array<Rule>;
  /** set to true if you want to exit on an already existing non-zero exit code (it's simply forwarded) */
  forwardExitCode?: boolean;
}

It's recommended to use js/ts files in combination with the exported defineConfig function for autocompletion and more flexibility. Create a simple-commitlintrc.js f.e. like this

  // simple-commitlintrc.js
  import { defineConfig } from 'simple-commitlint/helpers'

  // -------------------
  // and ONE of the following possibilities
  // -------------------

  // possibility 1 (object within)
  export default defineConfig({ ... })

  // possibility 2 (function that returns an object within)
  export default defineConfig(() => ({ ... }))

  // possibility 3 (function that returns a promise with the object within)
  export default defineConfig(async () => ({ ... }))

usage

parameters

| name | purpose | | ---------- | ---------------------------------------------------------------------------------------------------------------------------- | | --git | the path for the COMMIT_EDITMSG | | --params | params to pass to validation functions | | --config | use a different name than simple-commitlintrc (name should be provided without extension, still allows all extensions then!) |

husky

Most likely you'll use this with husky. For that purpose setup husky and run npx husky add .husky/commit-msg "npx --no-install simple-commitlint --git $1" (pretty similar to the use of husky with the original commitlint).

simple example rules

defineConfig({
  rules: [
    {
      name: 'head-not-empty',
      valid({ title }) {
        return title.length > 0;
      },
    },
  ],
});
defineConfig({
  rules: [
    {
      name: 'body-not-directly-under-head',
      valid({ body }) {
        return body.split('\n')[0].trim().length === 0;
      },
    },
  ],
});
defineConfig({
  rules: [
    {
      name: 'jira',
      valid({ title }) {
        return /^[A-Z]+-\d+ ?(?:\/\/?|:) ?[^\/ ].*$/.test(title);
      },
    },
  ],
});

(required to add params, example within .husky/commit-msg)

  npx simple-commitlint --git $1 --params "$(git diff --name-only)"
defineConfig({
  rules: [
    {
      name: 'special-case',
      valid({ title, cli }) {
        if (cli.split('\n').some((path) => path.endsWith('fileABC.ts')))
          return /someSpecialTest/.test(title);

        return /defaultTest/.test(title);
      },
    },
  ],
});

upcoming

  • more examples (maybe on a separate page)
  • more flexibility (prolly giving prepareCommit more power)
  • improvements of the CLI output
  • ...