naganowl

seq 20 | xargs -I{} echo "Hi there {}"

naganowl

grep -lr \.coffee app/assets/ | xargs sed -i '' -e '/\.\./!s/coffee/js/g'

naganowl

# Get list of all files | Print out each line count | Remove final line total | Calculate average
find . -name *.scss | xargs wc -l | sed -e '$ d' | awk '{ total += $1; count++ } END { print total/count }'

naganowl

# Inspired by Stack Overflow Question 19151954
LINE_NO = `grep -n require $1 | tail -1 | cut -d: -f1`

sed ''"${LINE_NO}"' a \
text_to_add
' $1

naganowl

# Inspired by https://unix.stackexchange.com/questions/72739/how-to-remove-multiple-blank-lines-from-a-file
for i in `grep -rl classSelector app/assets/stylesheets/` ; do cat $i | awk '!NF {if (++n <= 1) print; next}; {n=0;print}' | tee $i; done

naganowl

const childProcess = require('child_process');

function runShell(cmd, args, options) {
  const output = childProcess.spawnSync(cmd, args, options);

  return output.stdout.toString();
};

// 1. With just the base command
const findCmd = `find app/assets -type f -name *.js -not \( -path *spec* \) -o -name *.coffee -not \( -path *spec* \)`;

naganowl

find app/assets -type f -name '*.scss' | sed -E 's|/[^/]+$||' | sort -u

naganowl

# Assumes two files present (`sel` and `filez`)
# OSX needs an empty zero length argument, which is quite difficult to escape if using the same type of quotations
# Inner file (`filez`) is used over a `find ... -exec` to cut down on repetitive operations
cat sel | xargs -I '{}' sh -c 'cat filez | xargs sed -i "" "s/{}//"'

naganowl

# https://stackoverflow.com/questions/18046456/excluding-a-directory-from-find-and-sed-rename
# https://stackoverflow.com/questions/9704020/recursive-search-and-replace-in-text-files-on-mac-and-linux
find app -type f -name '*.erb' -not \( -path 'app/views/helpers/*' \) -exec sed -i '' s/this/that/ {} +

# Given a file `sel` of strings, remove all instances of them in all other directories
for i in `cat sel` ; do echo $i | cut -c2- | find app -type f -name '*.erb' -not \( -path 'app/views/helpers/*' \) -exec sed -i '' "s/$i//" {} +; done

naganowl

There is a difference b/w a prerelease tag associated to a package version (https://docs.npmjs.com/misc/semver#prerelease-tags) and a package's distribution tag upon publish (https://docs.npmjs.com/cli/dist-tag#purpose).

Thus, given the URL schemas dictated by https://docs.npmjs.com/files/package.json#git-urls-as-dependencies it be possible to publish an npm package with both a prerelease tag on a version and a distribution tag to give two options for targetting within a library

The RFC behind the new semver notation specifies just a prerelease tag. It be worthwhile to publish some sort of distribbution tag to avoid clobbering the default latest tag that npm uses