npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

grunt-html-compare

v1.2.0

Published

Compares two HTML files, passing the result to a user defined function.

Readme

grunt-html-compare

Compares two HTML files, passing the result to a user defined function.

Build Status

Getting Started

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');

The "html_compare" task

Overview

In your project's Gruntfile, add a section named html_compare to the data object passed into grunt.initConfig().

result

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) {
        ...
      }
    },
  },
});

Options

options.ignoreMissingSrc

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.

options.ignoreSelectors

Type: String or String Array Default value: undefined

One or more CSS selectors that describe nodes to be ignored during the comparison.

Usage Examples

Default Options

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');
      }
    }
  },
});

Custom Options

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) {
      ...
    }
  },
});

Contributing

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.