[![npm][npm]][npm-url]
[![node][node]][node-url]
!npm
[![tests][tests]][tests-url]

src="https://webpack.js.org/assets/icon-square-big.svg">

HTML Webpack Plugin

Plugin that simplifies creation of HTML files to serve your bundles

Install

Webpack 5

``bash
npm i --save-dev html-webpack-plugin
`

`bash
yarn add --dev html-webpack-plugin
`

Webpack 4

`bash
npm i --save-dev html-webpack-plugin@4
`

`bash
yarn add --dev html-webpack-plugin@4
`

This is a webpack plugin that simplifies creation of HTML files to serve your webpack bundles. This is especially useful for webpack bundles that include a hash in the filename which changes every compilation. You can either let the plugin generate an HTML file for you, supply
your own template using lodash templates or use your own loader.

Sponsors

Thanks for supporting the ongoing improvements to the html-webpack-plugin!

Zero Config

The html-webpack-plugin works without configuration.
It's a great addition to the ⚙️ webpack-config-plugins.

Plugins

The html-webpack-plugin provides hooks to extend it to your needs. There are already some really powerful plugins which can be integrated with zero configuration

- webpack-subresource-integrity for enhanced asset security
- appcache-webpack-plugin for iOS and Android offline usage
- favicons-webpack-plugin which generates favicons and icons for iOS, Android and desktop browsers
- html-webpack-harddisk-plugin can be used to always write to disk the html file, useful when webpack-dev-server / HMR are being used
- html-webpack-inline-svg-plugin to inline SVGs in the resulting HTML file.
- html-webpack-exclude-assets-plugin for excluding assets using regular expressions
- html-webpack-include-assets-plugin for including lists of js or css file paths (such as those copied by the copy-webpack-plugin).
- html-webpack-injector to inject chunks in head or body (different locations ) of same html document.
- resource-hints-webpack-plugin to add resource hints for faster initial page loads using and
- link-media-html-webpack-plugin allows for injected stylesheet tags to have their media attribute set automatically; useful for providing specific desktop/mobile/print etc. stylesheets that the browser will conditionally download
- html-webpack-inline-style-plugin for inlining styles to HTML elements using juice. Useful for email generation automatisation.
- html-webpack-exclude-empty-assets-plugin removes empty assets from being added to the html. This fixes some problems with extract-text-plugin with webpack 4.
- webpack-concat-plugin for concat and uglify files that needn't to be webpack bundles(for legacy files) and inject to html-webpack-plugin.
- html-webpack-link-type-plugin adds a configurable mimetype to resources injected as links (such as adding type="text/css" to external stylesheets) for compatibility with "strict mode".
- csp-html-webpack-plugin to add Content Security Policy meta tags to the HTML output
- strict-csp-html-webpack-plugin to add a strict Content-Security-Policy (CSP) as a meta tag to the HTML output. A strict CSP is specifically efficient against XSS attacks.
- webpack-nomodule-plugin allows you to add a nomodule attribute to specific injected scripts, which prevents the scripts from being loaded by newer browsers. Good for limiting loads of polyfills.
- html-webpack-skip-assets-plugin Skip adding certain output files to the html file. Built as a drop-in replacement for html-webpack-exclude-assets-plugin and works with newer html-webpack-plugin versions
- html-webpack-inject-preload allows to add preload links <link rel='preload'> anywhere you want.
- inject-body-webpack-plugin is a simple method of injecting a custom HTML string into the body.
- html-webpack-plugin-django a Webpack plugin to inject Django static tags.
- html-webpack-inject-attributes-plugin add extra attributes to inject assetTags.
- js-entry-webpack-plugin creates webpack bundles into your js entry

Usage

The plugin will generate an HTML5 file for you that includes all your webpack
bundles in the head using script tags. Just add the plugin to your webpack
config as follows:

webpack.config.js

`js
const HtmlWebpackPlugin = require("html-webpack-plugin");

module.exports = {
entry: "index.js",
output: {
path: __dirname + "/dist",
filename: "index_bundle.js",
},
plugins: [new HtmlWebpackPlugin()],
};
`

This will generate a file dist/index.html containing the following

`html









`

If you have multiple webpack entry points, they will all be included with script tags in the generated HTML.

If you have any CSS assets in webpack's output (for example, CSS extracted with the mini-css-extract-plugin)
then these will be included with tags in the HTML head.

If you have plugins that make use of it, html-webpack-plugin should be ordered first before any of the integrated Plugins.

Options

You can pass a hash of configuration options to html-webpack-plugin.
Allowed values are as follows:

| Name | Type | Default | Description |
| :----------------------: | :--------------------------------------------------: | :---------------------------------------------------: | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| title | {String} | Webpack App | The title to use for the generated HTML document |
| filename | {String\|Function} | 'index.html' | The file to write the HTML to. Defaults to index.html. You can specify a subdirectory here too (eg: assets/admin.html). The [name] placeholder will be replaced with the entry name. Can also be a function e.g. (entryName) => entryName + '.html'. |
| template | {String} | | webpack relative or absolute path to the template. By default it will use src/index.ejs if it exists. Please see the docs for details |
| templateContent | {string\|Function\|false} | false | Can be used instead of template to provide an inline template - please read the Writing Your Own Templates section |
| templateParameters | {Boolean\|Object\|Function} | false | Allows to overwrite the parameters used in the template - see example |
| inject | {Boolean\|String} | true | true \|\| 'head' \|\| 'body' \|\| false Inject all assets into the given template or templateContent. When passing 'body' all javascript resources will be placed at the bottom of the body element. 'head' will place the scripts in the head element. Passing true will add it to the head/body depending on the scriptLoading option. Passing false will disable automatic injections. - see the inject:false example |
| publicPath | {String\|'auto'} | 'auto' | The publicPath used for script and link tags |
| scriptLoading | {'blocking'\|'defer'\|'module'\|'systemjs-module'} | 'defer' | Modern browsers support non blocking javascript loading ('defer') to improve the page startup performance. Setting to 'module' adds attribute type="module". This also implies "defer", since modules are automatically deferred. |
| favicon | {String} | | Adds the given favicon path to the output HTML |
| meta | {Object} | {} | Allows to inject meta-tags. E.g. meta: {viewport: 'width=device-width, initial-scale=1, shrink-to-fit=no'} |
| base | {Object\|String\|false} | false | Inject a base tag. E.g. base: "https://example.com/path/page.html |
| minify | {Boolean\|Object} | true if mode is 'production', otherwise false | Controls if and in what ways the output should be minified. See minification below for more details. |
| hash | {Boolean} | false | If true then append a unique webpack compilation hash to all included scripts and CSS files (i.e. main.js?hash=compilation_hash). This is useful for cache busting |
| cache | {Boolean} | true | Emit the file only if it was changed |
| showErrors | {Boolean} | true | Errors details will be written into the HTML page |
| chunks | {?} | ? | Allows you to add only some chunks (e.g only the unit-test chunk) |
| chunksSortMode | {String\|Function} | auto | Allows to control how chunks should be sorted before they are included to the HTML. Allowed values are 'none' \| 'auto' \| 'manual' \| {Function} |
| excludeChunks | {Array.} | | Allows you to skip some chunks (e.g don't add the unit-test chunk) |
| xhtml | {Boolean} | false | If true render the link tags as self-closing (XHTML compliant) |

Here's an example webpack config illustrating how to use these options

webpack.config.js

`js
{
entry: 'index.js',
output: {
path: __dirname + '/dist',
filename: 'index_bundle.js'
},
plugins: [
new HtmlWebpackPlugin({
title: 'My App',
filename: 'assets/admin.html'
})
]
}
`

$3

To generate more than one HTML file, declare the plugin more than
once in your plugins array

webpack.config.js

`js
{
entry: 'index.js',
output: {
path: __dirname + '/dist',
filename: 'index_bundle.js'
},
plugins: [
new HtmlWebpackPlugin(), // Generates default index.html
new HtmlWebpackPlugin({ // Also generate a test.html
filename: 'test.html',
template: 'src/assets/test.html'
})
]
}
`

$3

If the default generated HTML doesn't meet your needs you can supply
your own template. The easiest way is to use the template option and pass a custom HTML file.
The html-webpack-plugin will automatically inject all necessary CSS, JS, manifest
and favicon files into the markup.

Details of other template loaders are documented here.

`js
plugins: [
new HtmlWebpackPlugin({
title: "Custom template",
// Load a custom template (lodash by default)
template: "index.html",
}),
];
`

index.html

`html








`

If you already have a template loader, you can use it to parse the template.
Please note that this will also happen if you specify the html-loader and use .html file as template.

webpack.config.js

`js
module: {
loaders: [
{ test: /\.hbs$/, loader: "handlebars-loader" }
]
},
plugins: [
new HtmlWebpackPlugin({
title: 'Custom template using Handlebars',
template: 'index.hbs'
})
]
`

You can use the lodash syntax out of the box. If the inject feature doesn't fit your needs and you want full control over the asset placement use the default template of the html-webpack-template project as a starting point for writing your own.

The following variables are available in the template by default (you can extend them using the templateParameters option):

- htmlWebpackPlugin: data specific to this plugin

- htmlWebpackPlugin.options: the options hash that was passed to
the plugin. In addition to the options actually used by this plugin,
you can use this hash to pass arbitrary data through to your template.

- htmlWebpackPlugin.tags: the prepared headTags and bodyTags Array to render the , ,