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

@sinchsmb/commit

v0.1.1

Published

Shared Commitlint configuration for the SinchSMB frontend

Downloads

17

Readme

sinchsmb/commit

Shared commitlint configuration for the SinchSMB frontend.
Based on the @commitlint/config-conventional config.

The config is validated by this json schema.

You can read more about the conventional commits here: https://www.conventionalcommits.org/en/v1.0.0/

It is recommended to use these packages to get a full cycle of consistent commits:

Read more in the docs.

This package also provides a command to automatically setup the above packages.

npx @sinchsmb/commit init

This command will:

  • Install and setup the husky package if it isn't installed
  • Install packages (@commitlint/cli, @commitlint/cz-commitlint, commitizen)
  • Setup hooks (prepare-commit-msg, commit-msg)
  • Create configuration files (.cz.json, .commitlintrc.json)

You can achieve the same result by following the steps below.

Install and setup the husky package

npm install husky --save-dev
npm set-script prepare "husky install"
npm run prepare

Install commitizen, commitlint, commitlint adapter for commitizen, config for commitlint.

npm install @sinchsmb/commit @commitlint/cli @commitlint/cz-commitlint commitizen --save-dev

Setup the prepare-commit-msg hook (commitizen)

npx husky add .husky/prepare-commit-msg "exec < /dev/tty && npx cz --hook || true"
git add .husky/prepare-commit-msg

Setup the commit-msg hook (commitlint)

cat <<EEE > .husky/commit-msg
#!/bin/sh
. "\$(dirname "\$0")/_/husky.sh"

npx --no -- commitlint --edit "\${1}"
EEE

Npx will swallow the "${1}" string so, please, use the command above.

chmod a+x .husky/commit-msg
git add .husky/commit-msg

Copy .cz.json and .commitlintrc.json from src/config into the project root.

IDE users warning

The prepare-commit-msg hook doesn't work (silently skipped) when run through the IDE. It requires an interactive terminal. However, you can use an IDE plugin to properly format the commit message.

  • WebStorm plugin: https://plugins.jetbrains.com/plugin/13389-conventional-commit