then the following convention might help: Here we've wrapped the code in an anonymous function, and invoked it immediately (thanks to the set of parens at the end). But JSLint Stops Scanning Yeah, sometimes it does. I have tried to remain neutral in all my posts on JSLint messages to date. Here, however I am going to jump off the fence and offer a sentiment of bafflement. JSLint deems some errors so serious that it immediately ceases scanning. For me this is understandable in the event that it encounters utterly unparsable code and literally cannot continue, however, I just don't understand why it must stop dead with the following: [...] and tabs (JSLint Style Guide) Move the invocation into the parens that contain the function. Move 'var' declarations to the top of the function. Nested comment. Nested not. Only properties should be deleted. Read only. Redefinition of [...]