jslint

The javascript, when run through JSLint yells at me and I am not sure why. /*jslint browser: true, devel: true, evil: true, undef: true, nomen: true, eqeqeq: true, plusplus: true, bitwise: true, newcap: true, immed: true */ var foo = function() { try { console.log('foo'); } catch(e) { alert(e); } try { console.log('bar'); } catch(e) { alert(e); } }; foo(); It tells me: Problem at line 12 character 11: 'e' is already defined. } catch(e) { It appears to be upset that I have a second catch(e) . Why would this be an issue? Does it not simply set e to local variable inside the catch block? Do I

I'm looking for something that works like Checkstyle for JavaScript. I know about JSLint and I'm already using Google's Closure compiler, but these mostly check for syntactic issues. Checkstyle can check for braces on the wrong line, but it also makes it possible to write custom checks like don't use HashMap. I'm looking for something like that for an upcoming JavaScript project. Any ideas? Google Closure Linter: http://code.google.com/closure/utilities/ "The Closure Linter is a utility that checks JavaScript files for style issues such as operator placement, missing semicolons, spacing, the

JSLint insists that my use of the somewhat exotic tilde operator in the below example is unexpected. What I’m wondering is whether this is a limitation of JSLint? or strict mode? or what else am I missing? (function () { 'use strict'; if (~'foo'.indexOf('bar')) { return 'wild accusations'; } }()); Also, why shouldn’t I use the simple-looking tilde operator instead of the more complex example below? Surely there must be a good reason not to? if ('foo'.indexOf('bar') >= 0) { … } From the JSLint Docs : Bitwise Operators JavaScript does not have an integer type, but it does have bitwise operators.

The following code passes JSLint: var sGreeting = 'hello world'; switch (sGreeting) { case 'Hello world!': var a = 'some a value'; break; case 'Kamusta mundo!': var b = 'some b value'; break; case 'Salut le Monde!': var c = 'some c value'; break; default: break; } However, once I put that code in a function, JSLint complains that I should Combine ... with the previous 'var' statement. If I follow JSLint, I would be defining variables that may never need to be used. How should I deal with this problem? Here's the code followed by JSLint's errors: function foo() { 'use strict'; var sGreeting =

Why is it considered best practise to put a ; at the end of a function definition. e.g. var tony = function () { console.log("hello there"); }; is better than: var tony = function () { console.log("hello there"); } TL;DR: Without a semicolon, your function expression can turn into an Immediately Invoked Functional Expression depending on the code that follows it. Automatic semicolon insertion is a pain. You shouldn't rely on it: var tony = function () { console.log("hello there"); // Hint: this doesn't get executed; }; (function() { /* do nothing */ }()); Versus: var tony = function () {