3 A command line interface and npm package for jshint.
7 To use jshint from any location (for npm v1.x) you need to install using the global (-g) flag.
15 You can also require JSHint itself as a module.
17 var jshint = require('jshint');
19 Note: If you are using npm v1.x be sure to install jshint locally (without the -g flag) or link it globally.
21 ## Text Editor Plugins
23 * [gedit-node-jshint](https://github.com/niftylettuce/gedit-node-jshint) - Simply use CTRL+J in gedit to run JSHint using `node-jshint`.
24 * [vim syntastic](https://github.com/scrooloose/syntastic) - Run node-jshint at each file save.
25 * [sublime-jshint](https://github.com/uipoet/sublime-jshint) - `F7` or `command-B` on any .js file. `F4` next error line,column. `shift-F4` previous error line,column.
29 Specify a custom reporter module (see example/reporter.js).
31 --reporter path/to/reporter.js
33 Use a jslint compatible xml reporter.
37 Show additional non-error data generated by jshint (unused globals etc).
41 ## Configuration Options
43 **Note:** This behavior described below is very different from versions prior to `0.6`.
45 The CLI uses the default options that come with JSHint.
47 Only one extra option is unique to node-jshint: `globals`
48 allows you to define an object of globals that get ignored for every file.
49 To see an example you can look at how whitelisted globals are defined
50 in the [jshint code](https://github.com/jshint/jshint/blob/c047ea1b01097fcc220fcd1a55c41f67ae2e6e81/jshint.js#L556)
52 To have your own configuration apply, there are several methods you can use:
56 Setting the `--config=/path/to/your/config` command line option to specify your own configuration file outside of the directory tree for your project.
58 ### Within your Project's Directory Tree
60 When the CLI is called, and a configuration file isn't specified already, `node-jshint` will attempt to locate one for you starting in `pwd`. (or "present working directory") If this does not yield a `.jshintrc` file, it will move one level up (`..`) the directory tree all the way up to the filesystem root. If a file is found, it stops immediately and uses that set of configuration.
62 This setup allows you to set up **one** configuration file for your entire project. (place it in the root folder) As long as you run `jshint` from anywhere within your project directory tree, the same configuration file will be used.
66 If all the methods above do not yield a `.jshintrc` to use, the last place that will be checked is your user's `$HOME` directory.
70 Default extension for files is ".js". If you want to use JSHint with other file extensions (.json), you need to pass this extra extension as an option :
74 ## Ignoring Files and Directories
76 If there is a .jshintignore file in your project's directory tree, (also provided you run `jshint` from within your project's directory) then any directories or files specified will be skipped over. (behaves just like a `.gitignore` file)
78 **Note:** Pattern matching uses minimatch, with the nocase [option](https://github.com/isaacs/minimatch). When there is no match, it performs a left side match (when no forward slashes present and path is a directory).
80 ## Installing dependencies for development
90 * All tests are passing.
91 * No (new) JSHint errors are introduced.