To avoid the warning defined but never used in jslint in your javascript add comments like: /*exported formValidationSetup, refreshErrorMessages */ In jshint and jslint you can set the unused option to false: /*jshint unused:false*/ See Options
I use acorn: $ acorn –silent tests/files/js-error.js; echo $? Unexpected token (1:14) 1 $ acorn –silent tests/files/js-ok.js; echo $? 0 Install via: npm -g install acorn.
That is indeed the correct way to name the enum, but the enum values should be ALL_CAPS instead of UpperCamelCase, like this: var WinnerEnum = { PLAYER_1: 1, PLAYER_2: 2, DRAW: 0 }; This is similar to Java’s naming convention for enums. Some references: Google JavaScript Style Guide Stijn de Witt’s Blog Enumify documentation As … Read more
Update (February 2019) : Async/await are now supported as of version 2.10.1. Simply update your .jshintrc to use “esversion”: 9. (+Info : Version changelog) Update (july 2018) : Async/await will arrive with the release of JsHint 2.10.0. +info : https://github.com/jshint/jshint/pull/3273 The JSHINT developing community considers that: JSHINT should first support all the ES6 syntax before … Read more
As it has already been mentioned for Babel 6, it’s the transform-es2015-modules-commonjs preset which adds strict mode. In case you want to use the whole es2015 preset without module transformations, put this in your .babelrc file: { “presets”: [ [“es2015”, { “modules”: false }] ] } This will disable modules and strict mode, while keeping … Read more
jshint is not aware of node.js globals by default you need to inform it. add this comment to the top: /* jshint node: true */
JS variables do not have block scope, they have “function” scope (or sometimes global). The declaration (but not the assignment) is “hoisted” to the top of the function. jshint is warning you that you have two such declarations – your code is equivalent to: var someVar; var someVar; // warning! if (something) { someVar = … Read more
Copy & paste from the documentation: Switch statements By default JSHint warns when you omit break or return statements within switch statements: […] If you really know what you’re doing you can tell JSHint that you intended the case block to fall through by adding a /* falls through */ comment So in your case: … Read more
Since variable declarations are hoisted to the top of the scope in which they appear the interpreter will effectively interpret both versions in the same way. For that reason, JSHint and JSLint suggest moving the declarations out of the loop initialiser. The following code… for (var i = 0; i < 10; i++) {} for … Read more
You can just move the function outside the loop and pass a reference to it to map: function mapCallback(item) { return { id : item[0], title : item[1], }; } for (i = 0; i < Collection.length; i += 4) { data.push({ items: Collection.slice(i, i + 4).map(mapCallback) }); } Alternatively, you can use a JSHint … Read more