This fixes #23 for me, however I am not merging this into master until I see jshint updated again and these new scripts work. The longer-term fix for issues like this is to require that jshint is installed locally as a node module and use it instead of the jshint we are installing locally in the bundle.
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
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.
If autoupdate downloads jshint.js because it is out-of-date it now also updates package.json and runs: npm install --production
* 'master' of github.com:fgnass/jshint.tmbundle: FIX: corrects 2 bugs in patch 7119b3a handling the fetching of the jshint.js file from the new location on github. Corrects error in variable name and sets https port to 443. Fixed path for JSHint.js, they redid the site and now everything is on GitHub. Conflicts: Support/jshint-tm.js
…n GitHub. I changed the path to always download from master, which is probably unstable, but there's no stable branch AFAIK. Not having this causes an error message every time you save.
…d changed to use require.