nareshv/LABjs — comment on commit 80ce37e00351e0452e2f06f5c3366eb1a146eaad
File:  line 0
By getify:

in addition to the above noted bugs that have been introduced in this patch, I'm also not a fan of blindly adding extra = here and there just because the linter says to. `typeof`, `toString`, etc ALWAYS return a string. There is no case where they don't, and there's no case where they return a falsy string like "0". So the extra = is unnecessary and clutters the code and increases the size (albeit slightly).

also, who is the linter to tell me i can't put my semi-colon on a separate line if i have a comma-separated list. I do that style of line separation so that, during debugging, i can comment out any line in the list without creating a syntax error. the linter complaining about this is obviously confused about ASI and thinks that semi-colon on next line is dangerous. It plainly is not, and I think it provides a value and avoids the syntax bug of accidentally commenting out the ending semi-colon in a list.

i'm not a fan of forcing third-party libs to undergo linting, or to have to adhere to a certain style. take the code as-is. And moreover, don't use the LAB.js source code in your project. Use the pre-compiled, pre-minified version which has passed all necessary checks and tests. Lint your own code, and let third-party authors worry about linting theirs. If your linter can't be relaxed on LAB.js file, then just add it as an ingored file for the linter.