Automated HTML Inspection with Grunt.
Phantomjs-based HTML Inspector implementation in Grunt. Runs HTML Inspector by @philipwalton against an HTML page.
This plugin requires Grunt
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-html-inspector --save-dev
In your project's Gruntfile, add a section named
html-inspector to the data object passed into
gruntinitConfig'html-inspector':options:parameters: 'noglobals=true'all:src: pathjoin'example' 'example.html'
An array that represents the locations of the pages to be inspected.
A string value that represents a path to an override bridge for HTML Inspector and this task. Override the bridge to add/configure rules and change the way HTMLInspector is configured. (Goal is to pull as much of the config as possible into the Grunt config eventually.)
A string value that represents the query string parameters to be passed to the page.
An object representing options to be passed to
grunt-lib-phantomjs and thus subsequently to
phantomjs. This can include things like
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using
grunt before submitting a pull request.