Paul N Stickney

Using something like NodeClusters - or most other per-process implementations - would avoid the issue of needing to [vastly] rewrite ESLint. (Such implementations are strictly _not_ threading, but allow managed...

@gyandeeps My projects are not big enough, or computer slow enough, for me to really care either way. In cases where there are sizable projects of many files, on computers...

@ilyavolodin Try this: Start running 8 different eslint processes (over the same set of files should be fine, although it would be 'more fair' to break up the files into...

@IanVS That's pretty cool .. now if only it was built-in to my eslint grunt task :} (Okay, I could get it shimmed in pretty easy - but it'd still...

I'm still for 'per process' concurrency.

My current roundabout solution, run inside `onPrepare` of the Protractor configuration, which shims (what I believe to be) the jasmineRequire object into the global scope used by jasmine-promise: ``` if...