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

@woopidi/semantic-release

v1.2.0

Published

An easy way to setup sematic versioning and version releasing

Downloads

5

Readme

Semantic Release

This makes life easier to setup semantic release on your package.

1. Install

npm i -D @woopidi/semantic-release

2. Modify package.json file

Add a semantic release cli command to trigger the release

"scripts": : {
	"release": "semantic-release",
	"commit": "commitizen"
}

Change your package version to something like this:

"version": "0.0.0-semantic-versioning"

Add the husky hooks to your package file:

"husky": {
    "hooks": {
      "commit-msg": "commitlint -E  HUSKY_GIT_PARAMS"
    }
}

3. Add the .releaserc.json in your root directory

{
	"branches": [
		"master"
	],
	"plugins": [
		"@semantic-release/commit-analyzer",
		"@semantic-release/release-notes-generator",
		[
			"@semantic-release/gitlab",
			{
				"gitlabUrl": "<GITLAB_SERVER_URL>"
			}
		]
	]
}

4. Add the commitlint.config.js in your root directory

module.exports = {
	extends: [
		"@commitlint/config-conventional"
	],
	rules: {
		"subject-case": [
			2,
			"never",
			[
				"start-case",
				"pascal-case"
			]
		]
	}
}

5. Tag your initial version manually

npm tag v1.0.0 <LOG_HASH_GOES_HERE>
npm push origin v1.0.0

6. Finally you can run the release

npm run release