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

conventional-changelog-jquery

v6.0.0

Published

JQuery preset for conventional-changelog.

Downloads

5,766,740

Readme

conventional-changelog-jquery

ESM-only package NPM version Node version Dependencies status Install size Build status Coverage status

conventional-changelog jQuery preset.

Issues with the convention itself should be reported on the JQuery issue tracker.

Install

# yarn
yarn add -D conventional-changelog-jquery
# pnpm
pnpm add -D conventional-changelog-jquery
# npm
npm i -D conventional-changelog-jquery

JQuery Convention

Commit messages should describe what changed, and reference the issue number if the commit closes or is associated with a particular issue. Commit messages for all jQuery projects should look like this:

Component: Short Description

Optional Long Description

Fixes #xxx
Closes gh-yyy
Ref #zzz

Every commit must have a subject (the first line). Everything else is optional.

Subject

This is the first line. It consists of a component, like "Event" or "Autocomplete".

Long description

There are two line breaks between the subject and the long description. The description can have any length and formatting, like lists.

References

References to issues or pull requests go after the long description, each one on their own line.

  • Use Fixes when the commit fixes an open issue.

  • Use Closes when the commit closes an open pull request.

  • Use Ref when referencing an issue or pull request that is already closed or should remain open. Examples include partial fixes and commits that add a test but not a fix.

  • Always use "gh-xxx" for GitHub issues and pull requests within the same repository. Use "[user]/[repo]#xxx" when referencing an issue or pull request in another repository, e.g., "Closes jquery/jquery-ui#175".

Based on https://github.com/jquery/contribute.jquery.org/blob/master/pages/commits-and-pull-requests.md#commit-guidelines