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

@samokat/lint-release

v1.0.0

Published

Lint tool for compare version in git branch and package.json

Downloads

2

Readme

lint-version

Lint tool for compare version in git branch and package.json

TL;DR

Just install and start using. 😎

yarn add @samokat/lint-release --dev

yarn lint-release

What?

We store application version in package.json file and create separate git branch for every release. This tool enforce similar versions in two source.

In allows branches with names satisfying pattern release/X.X.X and strictly compare it with a version in package.json.

Examples

|package.json version|branch name |result | |:------------------ |:------------- |:-----:| |1.0.0 |master |✅ | |2.2.0 |development |✅ | |1.0.0 |feature/tl-12 |✅ | |2.2.0 |release/2.2.0 |✅ | |2.2.0 |release/2.2.1 |🛑 | |1.0.0 |release/2.2.0 |🛑 |

How?

You can use in tool on CI, or add git-hook for linting.

CI specific

In some cases, on CI we can't use git for retriving branch name and CI provide it in env variables. This tool supports specific args for that case.

Example If your CI provide BRANCH_NAME variable, you can just pass it to linter:

yarn lint-release --branch=$BRANCH_NAME

Husky example

Never allow commit with different versions in branch and package.json.

{
  // ...
  "husky": {
    "hooks": {
      "pre-commit": "yarn lint-release",
    }
  },
  // ...
}