jslint

Does JSLint have anything like JavaScript Lint's control comments (e.g. /*jsl:fallthru*/ ) to make it ignore certain passages? napoleonss Put /*ignore jslint start*/ before and /*ignore jslint end*/ after the code to be ignored. Ex: function ignore(){ /*ignore jslint start*/ var x; var y; /*ignore jslint end*/ } Or export JsLint settings, define your IgnoreErrorStart/ IgnoreErrorEnd symbols and import. Edit Some folks may confuse this answer with JSHint. In that case, use these: /*jshint ignore:start*/ <!-- code in here --> /*jshint ignore:end*/ Taken from https://stackoverflow.com/a/26012357

I'm using JSLint to verify most of my external Javascript files, but the largest amount of errors I'm getting is from functions being used before they're defined. Is this really an issue I should worry about ? It seems Firefox, IE7 and Chrome don't care. Functions like the popular init() (which I use often) normally stick at the top as that makes sense to me (I like to pretend it's analogous to main() ) will, according to JSLint, need to be pushed to the bottom of the file. Steve Harrison If you declare functions using the function keyword, you can use them before they're declared. However, if

Hi I have the 3 javascript files. jquery.js utility.js file1.js In file1.js I have jQuery.noConflict() jQuery(document).ready(function($) { // .... }); I get an error 'jQuery' was used before it was defined. and 'document' was used before it was defined. How do I safely get rid of this warning. If I do var document = document || {}; then in my utility.js if it is used, it would be null in IE and ok in firefox. What is the best solution to this? From the documentation JSLint also recognizes a /*global */ directive that can indicate to JSLint that variables used in this file were defined in

I ran JSLint on this JavaScript code and it said: Problem at line 32 character 30: Missing radix parameter. This is the code in question: imageIndex = parseInt(id.substring(id.length - 1))-1; What is wrong here? Jayendra It always a good practice to pass radix with parseInt - parseInt(string, radix) For decimal - parseInt(id.substring(id.length - 1), 10) If the radix parameter is omitted, JavaScript assumes the following: If the string begins with "0x", the radix is 16 (hexadecimal) If the string begins with "0", the radix is 8 (octal). This feature is deprecated If the string begins with any

JSLint site updated, and I cannot check JS scripts anymore. For me, this warning is not critical, and I don't want to go through thousands of lines to fix this, I want to find more critical problems. Does anybody know how to turn off this error, or use legacy JSLint? UPDATE Example: function doSomethingWithNodes(nodes){ this.doSomething(); for (var i = 0; i < nodes.length; ++i){ this.doSomethingElse(nodes[i]); } doSomething(); // want to find this problem } jslint.com output: Error: Problem at line 4 character 8: Move all 'var' declarations to the top of the function. for (var i = 0; i < nodes

This question already has an answer here: Why to avoid creating objects in JavaScript? 2 answers I entered this statement in JSLint: var number = new Number(3); And received the following message: Do not use Number as a constructor. Why is that? The statement is creating a number object, not a primitive value, so I don't see why using new is a problem. EDIT: Thanks for all the responses. They've got me thinking further, so I posted a follow-up question here . In addition to breaking === and typeof returning "object", using the Number constructor also changes the way the value is used in