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

cz-aop-changelog

v1.0.5

Published

Commitizen rules about aop for standardized commit msg

Downloads

1

Readme

cz-aop-changelog

Commitizen rules about aop for standardized commit msg

commit-message规范:

  • 参考Angular官方的commit-message规范,由type, scope, subject, body, footer部分组成
  • typescope各有一套枚举值,用于指明本次提交的类型影响面,cr阶段会重点关注提交人是否对改动进行合理的拆分后再提交
  • subject是本次提交的简要主题,字符数至少8个,最多64个,不支持换行,并以.号结尾
  • type, scope, subjectheader部分,占整个commit-message的第一行
  • body是本次提交的详细描述,与header间隔1行,body部分至少1行,最多2行,每行字符数至少8个,最多64
  • footer是本次提交的icafe描述,与body间隔1行,footer部分只有1行,格式为icafe: fc-native-thrd-<ID>,可用Tab完成自动提示
  • 使用npm run commit提交时,对上述规范都有校验,保证提交操作的高效和有效,其他提交方式请自行保证commit-message规范,否则无法通过最终的校验

type枚举值参 /src/types/index.js

scope枚举值参 /src/scopes/index.js