Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
- The use of error markers is now optional. Unless error markers are enabled in the JSHint preference page, all JSHint errors are treated as warnings #71
- Comments are now also supported in the JSHint config for the workspace #76
- Fixed a LinkageError related to minimal-json #95, #99 (thanks to @piotrtomiak)
- Upgraded to JSHint 2.5.6
- JSHint errors are now displayed as errors instead of warnings (thanks @ben8p!) #45
jshintrcfiles can now be imported and exported from the Configuration page
- Links in the preference pages can now be opened in Eclipse's internal browser
- Several issues related to marker offsets have beed fixed (thanks @gurok!) #51
- The built-in JSHint has been upgraded to 2.1.10
- The built-in JSON parser has been updated to fix an error when editing the configuration (ralfstx/minimal-json#16)
- jshint-eclipse is now available in the Eclipse Marketplace (thanks @paulvi!) #65
- A continuous integration build is now running at Travis CI (thanks @paulvi!) #66
Project specific configurations are now read from a
.jshintrc file in the project root. This allows to share configurations with other tools.
JSHint configuration files are simple JSON that contains options for JSHint and global variables. Details on the format and available options can be found on the jshint pages.
This configuration format replaces the “options” and “globals” settings. The JSHint property pages allow to edit the config files directly and initialize them with the old project settings.
In order to support this configuration style, it was necessary to drop support for legacy JSLint.
Just a minor update to fix the severe performance drop that has been introduced in the recent version by including jshint 1.1.0 (#43). The problem has been fixed in jshint and the performance is back to normal.
A bug that prevented the plug-in from starting in Eclipse 3.6 has been fixed. #30
The built-in JSHint has been upgraded to version 2.1.2.
This version adds support for non-boolean options such as
A bug that caused a runtime exception for certain input files has been fixed. #34
The built-in JSHint has been upgraded to version 1.1.0.
This is a bugfix release, it updates the built-in JSHint and fixes a number of issues such as an off-by-one shift in marker positions and a problem with wild JSHint errors caused by an interference with another rhino version in the IDE.
The built-in JSHint has been upgraded to version r12.
This update introduces a new way of selecting the files and folders to be validated, based on include and exclude patterns. This allows for finer-grained control, e.g. including all
*.js files but excluding
*.min.js files, or excluding files in a build target folder.
The include and exclude patterns must be configured in the project’s properties, but a global preference page is planned for a future version.
The built-in jshint has been updated to the newest version r07.
A bug that prevented jshint-eclipse from running on Eclipse 3.6 has been fixed. #13