Skip to content

Replace [chunkhash] with [contenthash] #2098

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 4, 2018
Merged

Replace [chunkhash] with [contenthash] #2098

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
753118a
Replace [chunkhash] with [contenthash]
FadySamirSadek May 3, 2018
556c92f
Merge branch 'master' into patch-4
montogeek Aug 4, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions src/content/guides/caching.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ contributors:
- jouni-kantola
- skipjack
- dannycjones
- fadysamirsadek
- afontcu
related:
- title: Issue 652
Expand All @@ -21,7 +22,7 @@ This guide focuses on the configuration needed to ensure files produced by webpa

## Output Filenames

A simple way to ensure the browser picks up changed files is by using `output.filename` [substitutions](/configuration/output#output-filename). The `[hash]` substitution can be used to include a build-specific hash in the filename, however it's even better to use the `[chunkhash]` substitution which includes a chunk-specific hash in the filename.
A simple way to ensure the browser picks up changed files is by using `output.filename` [substitutions](/configuration/output#output-filename). The `[hash]` substitution can be used to include a build-specific hash in the filename, however it's even better to use the `[contenthash]` substitution which is the hash of the content of a file, which is different for each asset.

Let's get our project set up using the example from [getting started](/guides/getting-started) with the `plugins` from [output management](/guides/output-management), so we don't have to deal with maintaining our `index.html` file manually:

Expand Down Expand Up @@ -55,7 +56,7 @@ __webpack.config.js__
],
output: {
- filename: 'bundle.js',
+ filename: '[name].[chunkhash].js',
+ filename: '[name].[contenthash].js',
path: path.resolve(__dirname, 'dist')
}
};
Expand Down Expand Up @@ -124,7 +125,7 @@ __webpack.config.js__
      title: 'Caching'
],
output: {
filename: '[name].[chunkhash].js',
filename: '[name].[contenthash].js',
path: path.resolve(__dirname, 'dist')
},
+ optimization: {
Expand Down Expand Up @@ -168,7 +169,7 @@ __webpack.config.js__
}),
],
output: {
filename: '[name].[chunkhash].js',
filename: '[name].[contenthash].js',
path: path.resolve(__dirname, 'dist')
},
optimization: {
Expand Down Expand Up @@ -295,7 +296,7 @@ __webpack.config.js__
+ new webpack.HashedModuleIdsPlugin()
],
output: {
filename: '[name].[chunkhash].js',
filename: '[name].[contenthash].js',
path: path.resolve(__dirname, 'dist')
},
optimization: {
Expand Down