Webpack [contenthash] changes on file rename or if file is moved to another directory

Bug report

What is the current behavior? Contenthash depends on filename and target directory of source file.

If the current behavior is a bug, please provide the steps to reproduce.

1. Create a standard webpack config
2. Add the following to your webpack config:

  mode: 'production',
  ...
  output: {
    filename: '[name].[contenthash].js',
    clean: true
  }

1. Run webpack
2. Move your entry file to another directory or change it’s filename without modification of the file content.
3. Run webpack again
4. => Contenthash changed

What is the expected behavior?

Contenthash should only depend on the file content, not on the filename or the directory the file sits in. If the content does not change, the hash should stay the same.

Other relevant information: webpack version: webpack: 5.64.4, webpack-cli: 4.9.1 Node.js version: v14.15.4 Operating System: Windows Additional tools: Typescript

Related Issues: #1479

[Sebi2020]

@alexander-akait @vankop I will do so as soon as I find time to create a presentable minimal example.

[alexander-akait]

Expected, if you need real content hash you should enable https://webpack.js.org/configuration/optimization/#optimizationrealcontenthash, it is true by default in production mode, and disabled by default in development mode due perf