Bret Comnes bcomnes

Late 2016 Reading list

Late 2016 consisted of mostly module diving. Topics of focus related mainly to hyperamp and hyperblog, two experimental hypermodul.es projects.

	bret-mbr:testrun bret$ node generate.js
	key is <Buffer 09 19 de 78 56 e7 dc 1a a8 c4 88 d5 1a b9 5d e7 4c 20 5e 5c e6 6e 94 12 6e 14 4e b5 13 10 e7 ca>
	_stream_readable.js:561
	var ret = dest.write(chunk);
	^

	TypeError: dest.write is not a function
	at ReadStream.ondata (_stream_readable.js:561:20)
	at emitOne (events.js:96:13)
	at ReadStream.emit (events.js:188:7)

	class ReactComponent extends Component {
	constructor (props) {
	super(props)
	this.classMethod = this.classMethod.bind(this)
	}

	classMethod () {
	// do soemthing with 'this'
	}

-#!/usr/bin/env bash
-git branch -r --merged |
-  grep origin |
-  grep -v '>' |
-  grep -v 'master' |
-  xargs -L1 |
-  awk '{sub(/origin\//,"");print}' |
-  xargs git push origin  --delete

	PREPUBLISH AND PREPARE
	DEPRECATION NOTE
	Since [email protected], the npm CLI has run the prepublish script for both npm publish
	and npm install, because it's a convenient way to prepare a package for use (some
	common use cases are described in the section below). It has also turned out to
	be, in practice, very confusing https://github.com/npm/npm/issues/10074. As of
	[email protected], a new event has been introduced, prepare, that preserves this existing
	behavior. A new event, prepublishOnly has been added as a transitional strategy to
	allow users to avoid the confusing behavior of existing npm versions and only run
	on npm publish (for instance, running the tests one last time to ensure they're in

	tap 'caskroom/cask'
	tap 'caskroom/fonts'
	tap 'caskroom/versions'
	tap 'homebrew/binary'
	tap 'homebrew/boneyard'
	tap 'homebrew/bundle'
	tap 'homebrew/command-not-found'
	tap 'homebrew/completions'
	tap 'homebrew/core'
	tap 'homebrew/dupes'

	# 2017 New Years Reading List

	Here's what has my attention at the beginning of the new years.