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

helm-binary-testing

v1.2.12

Published

install helm binary to you node_modules

Downloads

3

Readme

helm-binary

Install helm via yarn/npm. This is a wrapper around the projects here: helm-binary-darwin helm-binary-linux

Global install

Taking the latest helm 3 binary at the time of writing (3.6.2) as an example:

yarn global add helm-binary@latest

npm should also work but I have seen places it can fail more ofter (like when running as the root user on a linux box).

npm install --global helm-binary@latest

Installation dependencies

Whatever linux/mac machine you run this on, make sure it has bash available as the postinstall script depends on that (#!/bin/sh isn't enough)

Package specific install

Add this package as a dependency and you can run helm from within your node runtime when using the scripts block of the package.json file.

Alternatively, appending the node_modules/.bin location when calling this from within your source code (through say, the exec package), e.g.

const helm = Path.resolve(__dirname, '../../node_modules/.bin/helm');

You are able to directly call helm within your source code without needing it to be installed on the running system.

Requirements

You've setup your $PATH correctly to have node binaries executable. e.g. My Ubuntu machine has: /home/edify42/.nvm/versions/node/v10.16.0/bin in my $PATH

How it works

It installs the optionalDependency based on your platform (darwin/linux) and then the postInstall script simply creates a hard link to the binary.

Automation

Github Actions support scheduled builds. Lets run one periodically to check the github releases API and package new versions of helm automagically for future use.

Publish notes for author/maintainer

ALWAYS run the yarn clean before yarn publish.

Hack innit

Is this a hack? Yes. I need to have helm available and this is a nice way of achieving it for some of the Javascript/Node tooling I currently work with.