JS lint returns a lot of errors, but code still works – good, bad?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
JSLint tells you information about the human-readability of the code. Considering what minified code looks like, I can tell you with confidence that the JavaScript parsing engine doesn’t give two hoots what the code looks like, as long as it is syntactically correct.
EDIT: I wouldn’t worry anyway. I just pasted my new project’s main JS file into it (52Kb, written using a coding style that I can read perfectly) and I got “Error: Too many errors” – and when I increased the maximum error count, it just said “Error: Stopping”. My code is apparently so unreadabe that JSLint gives up all hope of processing it after just 9% of the file! But if you were to look at it you’d probably be able to understand it just fine.