update jshint, add production node_modules/

Recent JSHint releases need the production node modules
listed in the jshint package.json file.
after new jshint download update production dependencies

If autoupdate downloads jshint.js because it is out-of-date
it now also updates package.json and runs:
  npm install --production
use custom .jshintrc options if they exist

If a custom .jshintrc exists use options defined there
instead of default options.

Look in the following places and if .jshintrc exists
return those options.

env.TM_DIRECTORY
- the directory of the current textmate file

env.TM_PROJECT_DIRECTORY
- the directory of the current text mate project

env.HOME
- users home dir

Otherwise return default options.
fix paths to .jshintrc and parse option files as JSON
add "Hint" (without save) command
close jshint window when no errors reported

When a jshint window with previous errors is visible
and a subsequent jshint check returns no errors,
close the jshint window.
fix accidental global var definition
use stream.Readable to get large files from stdin

The previous method was truncating files larger than
65535 bytes when piped in through stdin.

See: http://nodejs.org/api/stream.html#stream_class_stream_readable
small html styling updates
include and update other modules jshint loads

These modules are located in the same directory as
jshint.js and are loaded when jshint starts.

Update them when jshint.js is updated.
update readme

- describe new features
- jshint no longer works with JSC
- add new contributor