JSLint

[hobophobik]

Hi,

I've just completed installing SpiderMonkey on Centos so that I can run JSLint from the command line. So far it has proved a fantastic way to spot those annoying little extra commas that break our javascript in IE.

For a bit of amusement I decided to fire the Ext 3.2.1 source code through the tests; 99 files were perfect, while 182 files failed with at least one error.

Does anyone have any opinons about how strictly we should adhere to the amendments suggested in the JSLint output?

Cheers,
Hobo

[VinylFox]

Typically I use "The Good Parts" settings, but with "evil: true" included.

[mschwartz]

JSLint is a great help, but it's not perfect. In some functions, it will complain that not all paths return a value, but you do want it to return undefined for the path it complains about.

http://community.activestate.com/xpi...-jslint-komodo

^^^ awesomeness.

[hobophobik]

Hmm yes, I just tried it on our code with "The good parts".

white: true, onevar: true, undef: true, nomen: true, eqeqeq: true, plusplus: true, bitwise: true, regexp: true, newcap: true, immed: true

That's a lot of "Missing space after :" I'd have to fix. Also, due to the way I've split up classes into individual files, I get a lot of 'X is not defined' :/

[hobophobik]

http://community.activestate.com/xpi...-jslint-komodo

Shame, I stopped using Komodo a few months ago... vim all the way now

[mschwartz]

http://www.vim.org/scripts/script.php?script_id=2729

seems up to date.

For JavaScript, I love how Komodo highlights syntax errors as I type/edit.

vim is VERY powerful though.