Bugfix: Properly display the help screen if ESLint is not found on the PATH.

Bugfixes and performance improvements. (really)

• If running in a project, make sure eslint is started from the project directory so it picks up settings like .eslintignore.
• Fixed links from report view into your JavaScript file.
• Performance improvement when there are lots of gutter marks.

This is a major update.

• Instead of popping up the report window, problems are now reported as gutter marks right in the editor. The report window is still available by pressing Shift-Ctrl-V.
• The ESLint --fix command is now supported (auto-fix problems). You can select it from the Bundles menu, or by searching for it in the Select Bundle Item window (Ctrl-Cmd-T).
• The internals have been refactored.
  • Functionality is broken into separate modules.
  • Report generation is much cleaner using a lightweight templating system.

• Fixes issue #4, a bug which was caused by shell expansion of things that looked like fileglobs when they occurred as the output of an error message (in this case, a message that referenced /*, the beginning of a comment).

This update brings support for modern versions of ESLint.

• Native ESLint configuration cascading is now supported. This means you can have multiple, hierarchical rule sets. See [http://eslint.org/docs/user-guide/configuring.html](the ESLint documentation) for more information. (fixes #2)
• Errors related to an outdated version of ESLint are fixed. (fixes #5)
• Error reports now include a link to check for a newer version of this bundle.

• Don’t try to validate .eslintrc. Allow ESLint to do it. Now supports JSON-with-comments and YAML formats.

• Made it work again with the latest ESLint.
• Improved report layout that works better for users who choose to show command output in a pane below or to the right of the text view (instead of in a new window).

• Fix parsing of ESLint error report.

• Handle errors that have no ESLint rule reference.

Initial release.