Can't remember how sed works. Can't remember how cut works. I just don't have to use them often enough to commit them to memory. When I first read about jq, I thought Hmm, this is cool, but I love ES6. I know it well. Can't I just do all of this stuff in JS?

These days I'm too lazy to read manpages and learn tools like jq, sed, awk, etc. for things that I could I could write a JS expression for in ten seconds. All that was lacking was a basic command to handle the I/O. Just look how frigging easy stuff is:

npm install --global lambduh

> duh 'lines => lines.reverse()' somefile

> duh 'line => line.split(/\s+/g).reverse().join(", ")' names
Edwards, Andy
Doe, John

> cd ~ && npm install lodash
> echo 'Object.assign(global, require("lodash"))' >> ~/.lambduh.js

> duh 'lines => shuffle(lines)' somefile

> curl 'https://api.github.com/repos/facebook/react/commits?per_page=100' \
  | duh 'json => mapValues(groupBy(json, "commit.committer.name"), size)'
{
  "GitHub": 60,
  "Dan Abramov": 17,
  "Flarnie Marchan": 2,
  "Brian Vaughn": 3,
  "Nathan Hunzaker": 5,
  "Brandon Dail": 8,
  "Ben Alpert": 1,
  "Andrew Clark": 1,
  "Dominic Gannaway": 3
}

> curl 'https://api.github.com/repos/stedolan/jq/commits?per_page=2' \
  | duh 'json => json.map(({ commit: { message, committer: { name } } }) => ({ message, name }))'
[
  {
    "message": "Deal with strptime() on OS X and *BSD (fix #1415)\n\nstrptime() on OS X and *BSDs (reputedly) does not set tm_wday and\ntm_yday unless corresponding %U and %j format specifiers were used.\nThat can be... surprising when one parsed year, month, and day anyways.\nGlibc's strptime() conveniently sets tm_wday and tm_yday in those cases,\nbut OS X's does not, ignoring them completely.\n\nThis commit makes jq compute those where possible, though the day of\nweek computation may be wrong for dates before 1900-03-01 or after\n2099-12-31.",
    "name": "Nicolas Williams"
  },
  {
    "message": "Attempt to fix #1415\n\nOS X (and *BSD) strptime() does not set tm_wday nor tm_yday unless\ncorresponding format options are used.  That means we must call timegm()\nto set them.",
    "name": "Nicolas Williams"
  }
]

> aws cloudformation describe-stacks --stack-name clarity-db --query 'Stacks[0].Outputs' \
  | duh 'json => require("lodash").fromPairs(json.map(({OutputKey, OutputValue}) => [OutputKey, OutputValue]))'
{
  "DBInstance": "clarity",
  "RecordSet": "db.clarity.jcore.io",
  "SecurityGroup": "sg-31bbd643"
}

duh mv 'file => file.replace(/\.jsx$/g, ".js")' *.jsx

find . -name *.jsx | duh mv 'file => file.replace(/\.jsx$/g, ".js")'

duh mv 'file => { var [artist, album, file] = file.split(/\//g); return `${artist} - ${album} - ${file}` }' */*/*

The syntax that duh accepts for your function depends on the version of Node you're running. If you're running a really old version, you may not be able to use lambdas, and will have to resort to function () { return ... } instead.

You can use lambduh or just duh.

You may have noticed above that you can apply a transformation to each line of a plain text file. This is pretty much the only magic built into the duh command:

• If the first argument is mv (rather than a function), it runs in move mode.
• If the first argument of your function is lines (ignoring case), it runs in lines mode.
• Otherwise if the first argument of your function starts with l or L, it runs in line mode.
• If the first argument of your function starts with t or T, it runs in text mode.
• Otherwise, it runs in json mode.

⭐ 👍 Nice!! 👊 ✨

JSON.parses stdin or each file in the arguments, calls your function on it, writes JSON.stringify to stdout (or overwrites the input file with the result if you use the -i option). Duh!

Reads lines from stdin or each file in the arguments, one-by-one, calls your function on each with (text, lineNumber), and writes what it returns to stdout (or overwrites the input file with the result if you use the -i option), except:

• If your function returns false, it quits reading lines.
• If your function returns null or undefined, it skips to the next line without printing anything.

• --eol=EOL: (default: system line separator) specify line separator

Calls your function with an array of lines from stdin or each file in the arguments. If your function returns an array of lines, it writes them in order to stdout (or overwrites the input file with the result if you use the -i option). Otherwise, it calls String on it and outputs that string.

• --eol=EOL: (default: system line separator) specify line separator

Calls your function with the entire text from stdin or each file in the arguments in a single string, and writes what your function returns to stdout (or overwrites the input file with the result if you use the -i option).

• -i: (in place) overwrite input files with the result of the transformation
• --encoding=ENCODING: (default: utf8) specify file encoding

Move mode renames each file (or directory) in the arguments by applying your provided function (which must be the last argument) to each filename. If you don't provide any files in the arguments, or one of your arguments is a single dash (-), it will also read from stdin, treating each line as a filename.

By default it will print the old and new filenames and then ask for confirmation before actually moving them.

• -y: move the files without asking you to confirm the new names.
• --dry-run: just print out the old and new file names, then exit.

lambduh requires any .lambduh.js files in the working directory or its ancestors (from root to deepest), as well as .lambduh.js in your home directory. You can use these files to put functions on global scope so that you can use them in your function argument to lambduh. For example, here are some of the things I put in my ~/.lambduh.js:

Object.assign(global, require('lodash')) // put all lodash functions on context
global.replace = require('preserve-case') // case-preserving string.replace, often handy

With this I can do powerful stuff like:

> echo '{ "a": "foo bar", "b": "FOO BAR", "c": "it's all about the fooBar", "d": "foo-bar" }' \
  | duh 'json => mapValues(json, value => replace(value, "foo bar", "baz qux"))'
{
  "a": "baz qux",
  "b": "BAZ QUX",
  "c": "it's all about the bazQux",
  "d": "baz-qux"
}