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

@magda/ci-utils

v1.0.5

Published

A set of CI scripts that helps set up CI

Downloads

1,750

Readme

ci-utils

A set of CI scripts that helps set up CI.

check-helm-chart-version

Make sure the helm chart version is same as current Github Release Tag Name Version.

Usage:

yarn check-helm-chart-version [path to chart.yaml file of the chart...]

update-helm-chart-version

Update the version of all helm charts in a folder to a new version number.

Usage:

Add the following scripts entries to your package.json:

"add-all-chart-version-changes": "git ls-files -m | grep Chart.yaml | xargs git add && git ls-files -m | grep Chart.lock | xargs git add",
"add-all-helm-docs-changes": "helm-docs && git ls-files -m | grep -i readme.md | xargs git add",
"version": "yarn update-helm-chart-version && yarn update-all-charts && yarn add-all-chart-version-changes && yarn add-all-helm-docs-changes"

Then you can run:

npm version [new version number]

to set version.

Config Options

You can set the following fields in package.json to customize the helm chart version update behavior:

  • versionUpdateExclude:

    • Type: string[]
    • You can set versionUpdateExclude field of package.json to specify a list charts that should be excluded from changing version.
  • versionUpdateValues:

    • Type: { [chartName:string]: string[]; }
    • This field allow you to specify a list fields that should be update to current version in selected charts' "values" files.

    e.g. the following config:

    "versionUpdateValues": {
      "helm-chart-A": [
        "field1.field2.field3",
        "field4"
      ],
      "helm-chart-B": ["field5"]
    }

    will make the following fields:

    • helm-chart-A chart's "field1.field2.field3" & "field4" fields
    • helm-chart-Bchart's "field5" field

    set to the current package version.