I am using webpack-dev-server for development with html-webpack-plugin to generated the index.html with revision sources. The thing is every time I change the index.html the bundle system will not rebuild again. I know the index is not in the entry, but is there a way to solve this?
To tell Webpack dev server to serve index. html for any route, we can set the historyApiFallback. index property to 'index. html' .
The HtmlWebpackPlugin 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.
The problem is that index.html is not being watched by Webpack. It only watches those files that are "required" or "imported" somewhere in your code and the loaders are testing for.
The solution has two parts.
First require the index.html file in your entry point. Technically, you can require it anywhere in your application, but this is pretty convenient. I'm sure you could also just require your template if you were using a template with your html-webpack-plugin.
I required my index.html in my index.js file, which is my entry point:
require('./index.html')
const angular = require('angular')
const app = angular.module('app', [])
//...so on and so forth
Finally, install and add the raw-loader with all of your other loaders, to your Webpack config file. Thus:
{
test: /\.html$/,
loader: "raw-loader"
}
The raw loader will convert just about any file that is "required" into a string of text and, then, Webpack will watch it for you and refresh the dev-server every time you make a change.
Neither Webpack, itself, nor your program will actually do anything with the index.html file (or template) at the stage in which it is loaded. It's completely unnecessary for your production or testing environments, so just for good measure, I only add it if I'm running the development server:
/* eslint no-undef: 0 */
if (process.env.NODE_ENV === 'development') {
require('./index.html')
}
const angular = require('angular')
const app = angular.module('app', [])
//...so on and so forth
In theory you can "require in" a bunch of other static html files you'd like it to watch. ...or text files for that matter. I use the raw-loader, myself, for Angular directive templates, but I don't have to add those to the beginning of my entry point. I can just require inside the directive template property, like this:
module.exports = function(app) {
app.directive('myDirective', function(aListItem) {
return {
template: require('./myTemplate.html'),
restrict: 'E',
controller: function($scope) {
$scope.someThingThatGoesInMyTemplate = 'I love raw-loader!'
}
}
})
}
Simply add watchContentBase: true
to your devServer
's config. webpack-dev-server will watch for changes in all files that are located in contentBase
dir. Here we watch all files inside ./src
webpack.config.js:
...
devServer: {
port: 8080,
contentBase: './src',
watchContentBase: true
}
With webpack > 5.0
, use watchFiles
option
devServer: {
open: true,
watchFiles: ['src/**/*'],
},
From webpack > 5.x
, there are no contentBase
and watchContentBase
options
Instead you can do this:
devServer: {
watchFiles:['src/**/*'] // to detect changes on all files inside src directory
}
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With