The intent was to create an online demo of ESLint that runs in the browser (see: https://github.com/eslint/eslint.github.io/issues/3). Unfortunately, the person who was doing it dropped off the face of the earth and it never went anywhere.
Really the "eslint" object is what's being tested in the browser. We run that to make sure there are no Node.js-specific dependencies that have made it into that object. If that object works, then we can logically infer that the rules will work (since "eslint" runs the rules). It's a non-goal to have ESLint run in any specific group of browsers - we really just wanted a demo page so some people could play with it. On Tue, Oct 28, 2014 at 4:48 PM, Mathias Schreck < [email protected]> wrote: > I want to ask if ESLint should be able to run in the browser. > > At the moment we have some tests that run in phantomjs. I think this is > not very useful. We should either run all tests in browser or none. > > If we want to test ESLint in the browser I suggest to use karma and > browserify for the tests. That would be a long term solution for issue > #1406. > > -- > You received this message because you are subscribed to the Google Groups > "ESLint" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- ______________________________ Nicholas C. Zakas @slicknet Author, Professional JavaScript for Web Developers Buy it at Amazon.com: http://www.amazon.com/Professional-JavaScript-Developers-Nicholas-Zakas/dp/1118026691/ref=sr_1_3 -- You received this message because you are subscribed to the Google Groups "ESLint" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
