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

@we-mobius/commitizen

v0.0.7

Published

Install as development dependencies:

Downloads

3

Readme

Mobius Commitizen

Getting Started

Install as development dependencies:

pnpm add -D @we-mobius/commitizen

Using pnpm exec commit to commit your changes.

Or using pnpm exec cz to commit your changes, equipped with commitizen's functionality.

With commitlint

Install commitlint and husky as development dependencies:

pnpm dlx husky-init
pnpm install
pnpm add -D @commitlint/cli@latest

Using husky's command to add commitlint as commit-msg git hooks:

pnpm exec husky add .husky/commit-msg  'pnpm exec commitlint --edit ${1}'

Create a commitlint config file named .commitlintrc.json in the root directory of your project, with the following content:

{
  "extends": "@we-mobius/commitizen/commitlint"
}

Done, here we go, run git add . and pnpm exec cz to commit our changes.

Don't forget to add Commitizen friendly badge to your README.md: Commitizen friendly

[![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/)

Roadmap

  • [ ] Support fine-grained instructions for breaking parts and issue parts, see @commitlint/config-conventional.
  • [ ] Respect the commitlint configurations in the workspace root or the project root, using commitlint configurations to change the commitizen configurations.
  • [ ] Add commitizen-init command to initialize the commitizen -related configurations, including install necessary dependencies, adding commitlint configurations, adding git hooks, and so on. Then users can use pnpm dlx commitizen-init to get started, everything just works.
  • [ ] Reading commitizen.config.js to get the configurations; or reading configurations from valid commitlint config files. Functionalities commitlint provided will be integrated into Mobius Commitizen in the future, so commitizen.config.js will be the first config choice.

References