Compares two HTML files, passing the result to a user defined function.
This plugin requires Grunt ~0.4.5
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-compare --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-html-compare');
In your project's Gruntfile, add a section named html_compare
to the data object passed into grunt.initConfig()
.
Type: function
You must provide a result
parameter, which should be a function that takes a single boolean argument. The function will be invoked once the comparison result is known, with the first argument indicating the result (true if the files are the same, false otherwise). If the ignoreMissingSrc
option is set, the callback may also be called with undefined
, indicating that one or more of the src files were missing.
grunt.initConfig({
html_compare: {
options: {
// Task-specific options go here.
},
your_target: {
// Target-specific file lists and/or options go here.
result: function (result) {
...
}
},
},
});
Type: Boolean
Default value: false
Set this to true if you want to prevent the task from failing when the number of given source files is not exactly two. Instead, the task will silently complete without performing the comparison. Note that the result
function will be called with undefined
if one or more of the source files are missing.
Type: String
or String Array
Default value: undefined
One or more CSS selectors that describe nodes to be ignored during the comparison.
In this example, the default options are used to delete one of the two HTML files if they are the same.
grunt.initConfig({
html_compare: {
options: {},
src: ['a.html', 'b.html'],
result: function (result) {
if (result) {
grunt.file.delete('b.html');
}
}
},
});
In this example, the ignoreSelectors option is used to compare differences in two HTML files, whilst ignoring the last updated date. If there are no differences then the current file is kept, preserving the date.
grunt.initConfig({
html_compare: {
options: {
ignoreSelectors: '#lastUpdated'
},
src: ['index.html', 'index.new.html'],
result: function (result) {
if (result) {
grunt.file.delete('index.new.html');
} else {
grunt.file.delete('index.html');
// Rename using copy and delete
grunt.file.copy('index.new.html', 'index.html');
grunt.file.delete('index.new.html');
}
}
},
});
In this example, the ignoreMissingSrc files option is used to prevent failure when the index.html file is not available, due to performing a clean build.
grunt.initConfig({
html_compare: {
options: {
ignoreMissingSrc: true
},
src: ['index.html', 'index.new.html'],
result: function (result) {
...
}
},
});
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. If creating a new feature, consider opening an issue first, otherwise just submit a pull request.