Forums

Since any errors from JSLINT should be applied to the original source files, wouldn't it make more sense to run it on the source files?

Right now, if I make an error at line 3 of file src1.js, it might show three times, once at line 357 of built1.js, another at line 400 of built1-debug.js and a final one at line 60 of built1-min.js. You then have to go to any of them, go to the offending line, locate something that can help you find your bearings back in the source, go to src1.js and search by whatever piece you picked to locate it. Even finding which source it was takes some looking around.

Moreover, many JSLint errors make the YUI Compressor fail without giving any good information about what was it. It would be best to spare the compressing step if JSLint fails.

Also, at least in Windows Vista, the built script keeps going even after several errors. I usually get to the JSLint stage even when the YUI Compressor failed. If the order is reversed, I wouldn't want to continue if there are errors, so they remain right there in the screen and I don't get the screen cluttered with pointless messages from Java failing.

By the way, I post this here because I didn't see the YUI Builder available as a component/tool on the bug tracking.

I didn't look there, sorry. Since YUICompressor and YUIDoc are up there, I thought that, if it wasn't there, there wasn't any. Perhaps grouping all under a single Tools heading?

Thanks