JSHint obeys directives at a function level, so you can find the enclosing function and add a camelcase option to it. Here’s an example: /*jshint camelcase: true */ var not_camel_case = 1; // Warns function example() { /*jshint camelcase: false */ var not_camel_case = 2; // Does not warn }
If it’s a feature and not a bug, place this at the top of your file. /*jshint sub:true*/ If it’s a bug, you should refactor your code foo[‘tracker’] = bar // from this… foo.tracker = bar; // to this! Good post on the reasons here: https://stackoverflow.com/a/2001410/94668 As suggested by: @ThorSummoner you can use below in … Read more
Adding amd to env inside .eslintrc will enable you to use define() and require(), as per the amd spec: { “env”: { “amd”: true } }
It is extremely hard to detect this case without running the code. You can use option validthis to suppress this warning: “use strict”; var obj = { f: function() { this.prop = ‘value’; g.bind( this )(); } }; function g() { /*jshint validthis:true */ console.log( this.prop ); } It is to be noted that jshint … Read more
The filename should be .jshintrc, and the content is { “esversion”: 6 }
For JSHint you can create .jshintrc to your project directory with { “globals”: { “MyProject”: true } }
Add “use strict” at the top of your js file (at line 1 of your .js file): “use strict”; … function initialize_page() { var signin_found; /*Used to determine which page is loaded / reloaded*/ signin_found=document.getElementById(‘signin_button’); if(signin_found) { More about “use strict” in another question here on stackoverflow: What does “use strict” do in JavaScript, and … Read more
JSHint says “Possible strict violation” because you are using this inside something that, as far as it can tell, is not a method. In non-strict mode, calling gotoPage(5) would bind this to the global object (window in the browser). In strict mode, this would be undefined, and you would get in trouble. Presumably, you mean … Read more
Just to expand a bit, here’s a .jshintrc setup for Mocha: { …. “globals” : { /* MOCHA */ “describe” : false, “it” : false, “before” : false, “beforeEach” : false, “after” : false, “afterEach” : false } } From the JSHint Docs – the false (the default) means the variable is read-only. If you … Read more
You need to install jshint as well, that will sort out the issue. > npm install –save-dev jshint gulp-jshint