JSHint Maxing out CPU for many JS files

[jaboc83]

We have a large ASP.NET MVC project with around 400 script files. When we run jshint on build/save it brings our machines grinding to a halt because of a huge number of 'Evented I/O for V8 JavaScript (32 bit)' processes maxing out the CPU. I'm guessing these are threads spun off to lint each file, but it maxes out the CPU for around 30 seconds for us (Machines are running i5s with SSDs and 16Gb RAM) which is costly when we are used to a frequent save/build process. We don't really want to have to remember to run the linter manually.

[madskristensen]

I'm thinking we should remove the option to run JSHint on build. Same goes with LESS/CoffeeScript/Sass/etc. compilation

[SLaks]

No; compilation on build is very useful for many release processes.

Instead, we can make a weak dictionary of file paths to content hashes, and not re-lint any file that has not changed since it was last linted.

For compilation, that also needs to account for dependencies.
For both linting and compilation, it needs to account for the entire chain of config files.

[am11]

This is fixed with #381. There will be only one node.exe process running per devenv.

@madskristensen we can now close both this and #381.