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 🙏

© 2025 – Pkg Stats / Ryan Hefner

bashfury

v0.0.3

Published

BashFury: Shell pipelines with the goodness of JS templates I was stuck with a rather boring task today. I was planning to migrate from GitHub to GitLab, clean up the projects list and append some text to all the READMEs. I wanted to keep a copy at GitHub

Readme

BashFury: Shell pipelines with the goodness of JS templates I was stuck with a rather boring task today. I was planning to migrate from GitHub to GitLab, clean up the projects list and append some text to all the READMEs. I wanted to keep a copy at GitHub, but move active development to GitLab. With about 150 public and private repositories (of which I wanted to keep 40), this was the absolute worst way to spend my day. If your bash foo is up to the task, this would seem achievable. Mine wasn’t. I’ve written midsize scripts before, but all I could remember was the pain in dealing with arrays and strings. I’ve been dealing with a good bit of JS for a while though, and it would be nice if I could do the heavy lifting in JS and interleave shell commands wherever needed. Let’s make a tool for this. It’s called bashfury. npm install -g bashfury Spec and Documentation Execute JavaScript either from an external file, or directly from the command line. External JS files may export functions or data, but as the default export using ES6 syntax. 

cat square.js

export default function square(x) { return x ** 2; }

Inline eval

bashfury "square = x => x*x; square(10)" -p "echo ${x}"

From a file, square() being the default export

bashfury -f square.js 10 -p "echo ${x}"

  1. If the output of a JS execution is an array, the bash command will be called once for each item in the array.

cat numbers.js

export default const array = [1, 2, 3, 4];

Inline

bashfury "[1,2,3,4]" -p "echo ${x}"

With a file

bashfury -f numbers.js -p "echo ${x}"

  1. If the output of JS execution is an object, use the dot notation in the bash command template. bashfury "({ name: "jes", age: 57 })" -p "echo ${x.name}"

  2. If the output of JS execution is an array of arrays, treat x as an array. bashfury "[[1, 2, 3], [3, 4, 5]]" -p "echo ${x[0]*x[1]*x[2]}"

  3. If the output of JS execution is an array of objects, the obviously: bashfury "[{name: "jes"}, {name: "shob"}]" -p "echo ${x.name}"

  4. You can pipe the output further to more JS. And then again into a bash command and so on.

Inline

bashfury "[1,2,3,4]" -p "echo ${x}" -p "x => x**2"

With a file, with -pf

bashfury "[1,2,3,4]" -p "echo ${x}" -pf square.js

  1. If an item in an array is undefined, it’s swallowed.

Prints 1,2,4

bashfury "[1,2,undefined,4]" -p "echo ${x}"

  1. You could also access an array index in the template literal as the variable ‘i’.

Prints a1,b2,c3

bashfury "['a','b','c']" -p "echo ${x}${i}" That’s all guys. Report issues or ping me on Twitter.