Thanks! That worked really well for me. For others benefit I'll put a couple other details I found in here.
I needed to do was copy/paste the following global definitions at the top of my .js file (you may need to add/remove things if you're using different globals) /*global Events: false, Options: false, MooTools: false, Class: false, Element: false, typeOf: false, instanceOf: false, Fx: false, Slick: false, Type: false, Chain: false, Elements: false, Document: false, Event: false, Window: false, Browser: false, Hash: true, $H: true */ Then I could run my code through JSHint as long as I had the environments "Browser" and "jQuery" selected. I'm guessing that I needed jQuery turned on to understand the $ and other parts of the syntax that is similar. Thanks again for the quick response! On Mar 16, 8:48 am, Arian Stolwijk <[email protected]> wrote: > Yeah you need to define all the globals with /*globals: ...*/ > > A start is: > > /*globals: Events: false, Options: false, MooTools: false, Class: false, > Element: false, typeOf: false, instanceOf: false, Fx: false, Slick: false, > Type: false, Chain: false, Elements: false, Document: false, Event: false, > Window: false, Browser: false */ > > Personally I would recommend JSHint instead of JSLint at the moment. > > > > > > > > On Wed, Mar 16, 2011 at 1:41 PM, Jason G <[email protected]> wrote: > > I'm wondering if there's something out there that is similar to JSLint > > that is MooTools aware? JSLint iteslf throws a lot of errors when I > > send my code through it, and most seem to revolve around how things > > are defined in MooTools. > > > Thoughts/suggestions/ideas?
