Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Bryan here; guy behind CodeKit. I've tracked down an issue that I believe is attributable to JSHint. However, the explanation behind it is incredibly complicated so please bear with me.
I don't believe the issue is in my app, since I use the exact same code to run JSLint and that works just fine every time.
CONTENT BETWEEN QUOTES
The plot thickens. If I modify one of these "setTimeout" lines to look like this:
JSHint now runs correctly. However, as soon as I add any content between those quotation marks (other than a space), the exception is thrown and JSHint fails. Literally anything inside the quotes will do it --- a single letter, a function name, etc.
I've tried all sorts of various edits to these lines and this is what I've narrowed it down to. As long as nothing but spaces appear inside the quotation marks, JSHint runs fine.
The link below will take you to Dropbox, where I have posted a zip file containing two files. The first is the exact file as I received it from one of my users, with no changes. The second file is one where I have commented out each "setTimeout" line until I got JSHint to run correctly. You can use a file-difference tool to see the exact lines I commented out.
Please let me know if I can provide any additional information. Thanks for looking into this.
What version of JSHint? I assume something pre-1.0.0 since everything else doesn't support JSC anymore (and that's why it doesn't make sense to compare with JSHint website since the website always uses the latest version).
Do you combine everything on one file? Can you paste a gist of that file somewhere? I checked
I'm using 1.0.0. Also, I'm not running JSHint through the JSC shell. From your docs:
Bingo. As suggested by one of my followers here --> https://twitter.com/BenBornschein/status/309935445909839872
If you change the setTimeout line FROM this:
That's be really helpful, thanks!
On Sunday, March 10, 2013, bdkjones wrote: