ELLIOTTCABLE

Since http://stillmaintained.com is, ironically, no longer maintained, here's some custom GitHub badges for your dead, stale, or frozen projects:

: https://img.shields.io/badge/maintained%3F-no!-red.svg?style=flat
: https://img.shields.io/badge/maintained%3F-seeking:_help_me!-yellow.svg?style=flat
: https://img.shields.io/badge/maintained%3F-rapidly_changing!-orange.svg?style=flat
: https://img.shields.io/badge/maintained%3F-yes!-brightgreen.svg?style=flat
: https://img.shields.io/badge/maintained%3F-feature--frozen-lightgrey.svg?style=flat

You can modify these using [Shields.

	// ## Types

	type WalkFilterback<node,collection> = (
	current: node, parent: node
	, supplied: collection<node>, visited: collection<node>
	, callbacks: WalkCallback<node,collection>[]
	) => boolean \| void

	type WalkSupplyback<node,collection> = (
	current: node, parent: node

	# npm test
	chokidar --throttle 3500 --initial -c 'clear; npm --silent run-script test' -- \
	'./giraphe.es6.js' 'Tests/*/.js'

	# Flow
	chokidar --throttle 3500 --initial -c 'clear; flow' -- \
	'./giraphe.es6.js' 'Tests/*/.js'

	# git status
	chokidar --initial -c \

	So, this has been an excellent thread, and against all my expectations … I think @jmelfi et al. have
	actually swung me around. It's a really difficult question, and both sides keep bringing up really
	good points, but … there's something really important and subtle here:

	Buried in all the (if I'm being honest … super-silly.) ‘legal’ and ‘licensing’ talk¹, there's a
	pretty valid concern being raised here; and I think @isaacs brushes up against it in his recent
	replies: I'm starting to think that it may be acting in bad faith, for npm to disallow unpublishing
	in the main registry.

	1. Users expect a particular behaviour. There's a whole UX aspect to that, sure, and that's a

	First off, I need help; I've tried generating several, ridiculously
	(unnecessarily.) complex passwords to meet your system's silly rules,
	and with none of them, can I successfully get beyond the “your
	password has expired” page. I simply keep getting told “Password must be
	stronger! Password must be stronger!”, even when I've filled your damn
	little green bar up all the way. There's not even any feedback as to
	what the requirements are that I am apparently failing! (I cannot
	imagine what password requirements could be so draconian that these
	examples are failing the test: ‘password must require upper-plane
	Unicode?’ ‘individual bytes of characters must form a sequence, when

	// index.js
	module.exports = require('./Library/app');

	// Source/app.js.es6
	import from 'foo';
	import from 'bar';

	// Source/foo.js.es6
	console.log('simple');

	declare module 'child_process' {
	declare class Stream {}

	declare function spawn(command: string, args: Array<string>,
	options: { cwd: string, env: Object,
	stdio: string \| [?string \| number \| Stream]
	}
	) : void
	}

	node_modules/babel-core/lib/api/node.js:87
	87: function transformFile(filename /: string/, opts /:: ?: Object/, callback /: Function/) {
	^^^ Type annotations are not allowed in untyped mode

	node_modules/babel-core/lib/api/register/cache.js:73
	73: function get() {
	^ return. Missing annotation

	node_modules/babel-core/lib/api/register/node.js:23
	23: var _transformationFileOptionsOptionManager = require("../../transformation/file/options/option-manager");

	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
	<plist version="1.0">
	<dict>
	<key>CompatibleVersion</key>
	<integer>1</integer>
	<key>RawQuery</key>
	<string>((_kMDItemGroupId = 13))</string>
	<key>RawQueryDict</key>
	<dict>