Use custom options if they exist #16
Conversation
|
fyi: this pull request is based on the correct-path-to-hosted-jshint branch in #14 |
Recent JSHint releases need the production node modules listed in the jshint package.json file.
If autoupdate downloads jshint.js because it is out-of-date it now also updates package.json and runs: npm install --production
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.
|
Now this is based on include-jshint-npm-production-dependencies in #17 |
|
This now also removes |
|
Thank for your contributions! Since I no longer use TextMate I added you as collaborator to this projects so that you merge the PRs yourself. Again, thanks a lot for your work! |
|
Thanks Felix, Are you using SublimeText like most of the other people I work with? Since I've found the need to rebase some of these pull requests I'll keep using them for a few more days before merging. |
|
Yes, I'm currently using SublimeText 2 while I wait for Brackets to get mature enough to be usable ;) |
If a custom
.jshintrcexists 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 fileenv.TM_PROJECT_DIRECTORY: the directory of the current text mate projectenv.HOME: users home dirOtherwise return default options.