Well it looks like Douglas Crockford just made a whole lot more people switch to JSHint. Have a look at this commit. The “Mixed spaces and tabs” error has been removed, and a new “Use spaces, not tabs” error has been added in its place. Aside from that, there’s one tiny change in that diff … Read more
There’s no difference. Both are valid ways to get the JavaScript parser to treat your function as an expression instead of a declaration. Note that + and ! will also work, and are sometimes used by minifiers to save a character of size: +function() { var foo = ‘bar’; }(); !function() { var foo = … 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
Douglas Crockford has a new idiomatic way of achieving the above – his old technique was to use an inner function to bind the variables, but the new technique uses a function maker. See slide 74 in the slides to his “Function the Ultimate” talk. [This slideshare no longer exists] For the lazy, here is … Read more
Javascript does not have block scope. In other languages with it (like c), if you declare a variable in the if statement, you can not access it outside of it, but in javascript you can. The author of JSLint believes it is a bad practice, since you (or other readers) might get confused and think … Read more
array literal notation is where you define a new array using just empty brackets. In your example: var myArray = []; It is the “new” way of defining arrays, and I suppose it is shorter/cleaner. The examples below explain the difference between them: var a = [], // these are the same b = new … Read more
Ah, I’ve got this handled… I wrap the statements that use the underscore prefixed variables with JSLint commands to disable, then re-enable this class of error: /*jslint nomen: true*/ … statement(s) with _var … /*jslint nomen: false*/
To pass JSLint’s criteria, it needs to be written like this: }(jQuery)); Though I think that particular criteria is a bit subjective. Both ways seem fine in my opinion. (function () {})() makes a bit more sense to me since you wrap the full function, then call it (function () {}()) looks like you’re wrapping … Read more
Move the function outside the loop: function dummy() { return this.name_; } // Or: var dummy = function() {return this.name;}; for (var i = 0; i<processorList.length; ++i) { result[i] = { processor_: timestampsToDateTime(processorList[i]), name_: processorList[i].processorName, getLabel: dummy }; } … Or just ignore the message by using the loopfunc option at the top of the … Read more
/*jslint browser: true*/ Was the correct solution to this. As of 2017-07-07, you have to set the global directive manually. From the JSLint documentation: The /*global*/ directive is used to specify a set of globals (usually functions and objects containing functions) that are available to this file. This was commonly used in browsers to link … Read more