Eli Perelman

If you go down the road of wrapping webpack, you put a much higher maintenance burden on this library to keep webpack and its apis up to date, as well...

I think this would be resolved by https://github.com/FormidableLabs/electron-webpack-dashboard/issues/24#issuecomment-340222635.

Not to just say +1, but +1. Semver is great, but only when it is enforced automatically. In npm, that is not the case. Package maintainers sometimes make mistakes and...

Running with `DEBUG=*` shows nothing in the console when `.end`ing the logcat: ``` adb:command Send '000Chost:devices' +0ms adb:command Send '0017host:transport:94fdce73' +3ms adb:command Send '001Fshell:logcat -B *:I 2>/dev/null' +1ms ```

On OS X, using nettop: ``` adb.724 84 B tcp4 127.0.0.1:5037localhost:58777 lo0 Established 62 B tcp4 127.0.0.1:56672*:* lo0 Listen tcp4 127.0.0.1:56522*:* lo0 Listen tcp4 127.0.0.1:56519*:* lo0 Listen tcp4 127.0.0.1:5037localhost:49616 lo0...

Oooo, that's a good point. I wonder if we should revise the `eslintrc` command to actually set `useEslintrc` just when calling that method?

The `eslintrc` command is meant to be called from an eslintrc file, so calling the command should imply the existence of the file.

Oooooooo, this looks sooo nice! @edmorley thoughts on swapping out? @djmitche thoughts on publishing just the plugin to npm for us to consume?

@djmitche I mean just the plugin, not the middleware portion.

@djmitche yep! The monorepo doesn't rely on any external middleware, but we can rely on external plugins.