I tried to follow Dustin’s and STRML’s advice on this thread, and here’s what worked best for me. Development Setup I use Sublime Text with SublimeLinter + SublimeLinter-jshint + SublimeLinter-jsxhint. These are very nice plugins that let me see mistakes when I save the file, both for JS and JSX files: These plugins respect your … Read more
This works and is certainly valid. It’s especially useful in more complicated use cases, like nested ones. var a = test1 ? b : test2 ? c : d;
One way to tackle this is to modify your .jshintrc and set angular as one of the predefined variables, as Jayantha said. .jshintrc would look like this: { “predef”: [“angular”] }
I don’t think JSLint has an option to turn that off. JSHint (a fork with more options) has an option for it, though: The expr option, documented as “if ExpressionStatement should be allowed as Programs”.
So there is an option to ignore files in jshint, but it’s not set within .jshintrc but rather a separate file .jshintignore, which makes sense. However, while jshint will look for .jshintrc in your project’s subdirectories, .jshintignore needs to be in the project root. So with Twitter Bootstrap, .jshintrc is in /js while .jshintignore needs … Read more
The best place to look for things like that is the source (which is available on GitHub). The file you’re looking for is messages.js (versions: current release (2.9.5, 2017-06-22), master branch, 2.1.4 (source for the code below)): var warnings = { W001: “‘hasOwnProperty’ is a really bad name.”, W002: “Value of ‘{a}’ may be overwritten … Read more
It’s not possible to switch off this warning with a flag, and the JSHint maintainer doesn’t want to add a flag for this. However, it is possible to turn off warnings according to their number. In this case, you’d write: /* jshint -W099 */ If you’re using a JSHint configuration file, you can specify this … Read more
Here is a more updated info, there is a configuration to associate a file extension to a checker, in your .vimrc let g:syntastic_javascript_checkers = [‘jshint’] Also to get info about what’s going on run this command in vim :SyntasticInfo And you’ll get an output similar to this: Syntastic info for filetype: javascript Available checkers: gjslint … Read more
Put /*jshint bitwise: false*/ in the top of your file A list of available options: http://jshint.com/docs/options/
You can now add your preferred linters to Brackets’ preferences file: “language”: { “javascript”: { “linting.prefer”: [“JSHint”], “linting.usePreferredOnly”: true } }, Open the preferences file with Debug > Open Preferences File. Brackets preferences Example preferences.json file