How to install JSLint on Ubuntu: Install nodejs (includes npm, the Node Package Manager): sudo apt-get install nodejs Install node-jslint. either globally: sudo npm install -g jslint or locally, and include it in $PATH: npm install jslint and add this line to your.bashrc (adjust version number as appropriate) alias jslint=”~/.npm/jslint/0.1.8/package/bin/jslint.js”
From the JSLint docs: continue Statement Avoid use of the continue statement. It tends to obscure the control flow of the function. So take it out entirely if you want to conform to the conventions that JSLint follows.
That’s not valid JavaScript, it should be: $(document).ready(function() { So JSLint will (appropriately) complain about your syntax. If you want to get rid of the Implied global: $, document message, go to the bottom where it has Predefined (, separated), and put jQuery, $ in that textbox then run again. For the document piece, check … Read more
I believe this means you should move the function calling parens inside the wrapping parens (function() { /* code */ })() The two last parens that execute the function are the problem. This is how jslint wants it to look like: (function() { /* code */ }())
It looks a lot like a “can’t happen” check (a form of defensive programming). If so, there might not be any way to trigger it in practice.
In addition to breaking === and typeof returning “object”, using the Number constructor also changes the way the value is used in boolean contexts. Since “new Number(0)” is an object, not a literal value, it evaluates as “true” because it is not null. So for example: var n1 = 0; var n2 = new Number(0); … Read more
You can add this yourself to JSLint if you want, though that’s borderline Evil. Here’s one quick and dirty way with the current version: The route I’m going to take is to hijack the token function’s switch block for /* style comments. That’s at line 1276 currently: case ‘/*’: for (;;) { i = source_row.search(lx); … Read more
“Insecure” means “unspecific” in this context. Both the dot . and the exclusive range [^…] are not clearly defining what should be matched by the regex. For validation purposes, this can propose the risk of successfully matching stuff that you did not think of and do not want (think: white-listing vs. black-listing). In any case, … Read more
While it checks for different things than JSLint, the fixjsstyle mode of the Google closure linter may do what you want. It automatically fixes code to (more closely) fit with the Google Javascript style guide which is well worth a read. As others have pointed out, the Javascript beautifier is the way to go for … Read more
If keypairs is an array, then you should really iterate over the elements like: for(var i = 0; i < keypairs.length; i++) { … } If keypairs is a hash, then JSLint is correctly recommending that you check that you are operating on the appropriate key type (i.e., confirming that the hash is the expected … Read more