html-minify plugin for grunt
JavaScript
Switch branches/tags
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
tasks
test
.gitignore
.jshintrc
.travis.yml
Gruntfile.js
LICENSE-MIT
README.md
package.json

README.md

grunt-html-minify

Build Status Dependency Status

html-minify for grunt

Getting Started

This plugin requires Grunt ~0.4.1

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-minify --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-html-minify');

The "html_minify" task

Overview

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

grunt.initConfig({
  html_minify: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
})

Options

options.charset

Type: String Default value: 'utf-8'

A string value that is used to assign the input file encoding.

Usage Examples

normal(UTF-8 files)

grunt.initConfig({
  html_minify: {
    options: {},
    files: {
      'dest/whatever.html': ['src/whatever.html'],
    },
  },
})
grunt.initConfig({
    pkg: grunt.file.readJSON('package.json'),
    html_minify: {
      options: {
      },
      all: {
        files:[
        {
          expand: true,
          cwd: './',
          src: ['*.html'],
          dest: './test/',
          ext:'-min.html'}
          ]
        }
      }
    });

assign file encoding

grunt.initConfig({
  html_minify: {
    options: {
      charset:'gbk'
    },
    files: {
      'dest/whatever.html': ['src/whatever.html'],
    },
  },
})

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.

Release History

2013-06-27 first official release