Alan Wong 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

	# Get the files changed in SHA
	git diff-tree --no-commit-id --name-only -r <SHA> > theFiles

	# Inline replace and backup file (b/c of Mac) for leading newlines
	xargs -0 -n 1 sed -ie '/./,$!d'< <(tr \\n \\0 <theFiles)

	# Same as above, but for trailing newlines
	find . -type f -name '.coffee' -exec sed -ie -e :a -e '/^\n$/{$d;N;};/\n$/ba' {} \;

	# Remove the backup files (assuming only Coffee files changed)

	general:
	artifacts:
	- "log"
	- "npm-debug.log"
	- "yarn-error.log"

	machine:
	node:
	version: 6.10.1

	([]).map.call(document.querySelectorAll('.diffstat.tooltipped'), (n) => {
	const linesChanged = +n.innerHTML.match(/^\d+/)[0];
	if(linesChanged > 100) {
	// Log the line delta and the name of the file.
	console.log(n, n.parentNode.querySelector('a'));
	}
	return linesChanged;
	});

	@import './repeat.scss'

	#{repeat('.jasmine-passed', 15)} a {
	color: aliceblue !important;
	}

	// Invoke the first argument (needs to be a function), with `1` as the `this` context and `2` as the argument
	console.log.call.apply(a => a, [1, 2]) // -> 2

	console.log.call.apply(function(a,b) { return this.ab + a + b; }, [{ab: 19}, 2, 3]) // -> 24