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

@meludi/conventional-commits-config

v1.0.0

Published

Shareable conventional commits configuration

Downloads

22

Readme

@meludi/conventional-commits-config

NPM Package GitHub Workflow Status GitHub issues GitHub license Commitizen friendly

Shareable conventional commits configuration based on conventional commits.

Install

$ npm i -D @meludi/conventional-commits-config

Prepare

Husky

Edit package.json > prepare script and run it once:

$ npm pkg set scripts.prepare="is-ci || husky install"
$ npm run prepare

lint-staged

Add the following to your package.json:

...
"lint-staged": {
  "*.js": "eslint .",
  "*": "your_command",
  ...
}

Add husky hooks and scripts:

$ npx husky add .husky/pre-commit "npm run pre-commit"
$ npm pkg set scripts.pre-commit="lint-staged"

commitlint and commitizen

Create a commitlint.config.js configuration file in the root of your project and add the following to it:

// commitlint.config.js
module.exports = require('@meludi/conventional-commits-config/commitlint.config');

Add the following to your package.json:

...
"config": {
  "commitizen": {
    "path": "cz-conventional-changelog"
  }
}

Add husky hooks and scripts:

# commitlint
$ npx husky add .husky/commit-msg "npm run commitlint"
$ npm pkg set scripts.commitlint="commitlint --edit \$1"

# commitizen
$ npm pkg set scripts.commit="git cz"

Run it:

$ npm run commit

Recommendation

semantic-release - Fully automated version management and package publishing:

Setup Semantic Release on your GitHub repo

  • Create npm token using npm token create or https://www.npmjs.com/settings/YOUR_ACCOUNT_NAME/tokens
  • Add NPM_TOKEN to GitHub repo: Settings -> Secret and variables -> Secrets
  • Set write permission to GitHub repo: Settings -> Actions - General -> Workflow permissions -> Read and write permission
  • Set version to 0.0.0-semantic-release in package.json

GitHub Actions Example

configuration for Node projects

LICENSE

MIT