404 status code when using option { output.filename: '[name].[contenthash].js' } in webpack.config.js

[OptimistLabyrinth]

Bug report

What is the current behavior?

I apologize in advance that I'm not that good at English.

While I was following the webpack docs guide(https://webpack.js.org/guides/caching/),
I came across an issue.
I'm not sure if this is really an issue or not, but I think it could be problematic.
I tried 3 cases to figure out when the issue occurs and when it doesn't

I used webpack-dev-server to host my webpack bundled app.

package.json file

{
  "name": "webpack-any",
  "version": "1.0.0",
  "description": "",
  "private": "true",
  "scripts": {
    "start": "npm run build && webpack server --config webpack.prod.js",
    "build": "webpack --config webpack.prod.js",
    "dev": "npm run devBuild && webpack server --config webpack.config.js",
    "devBuild" : "webpack --config webpack.config.js",
    "clean": "rimraf ./prod/*",
    "devClean": "rimraf ./dist/*"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "dependencies": {
    "lodash": "^4.17.21"
  },
  "devDependencies": {
    "@babel/core": "^7.14.6",
    "@babel/preset-env": "^7.14.7",
    "babel-loader": "^8.2.2",
    "css-loader": "^6.1.0",
    "csv-loader": "^3.0.3",
    "html-loader": "^2.1.2",
    "html-webpack-plugin": "^5.3.2",
    "rimraf": "^3.0.2",
    "style-loader": "^3.1.0",
    "webpack": "^5.45.1",
    "webpack-cli": "^4.7.2",
    "webpack-dev-server": "^3.11.2",
    "webpack-manifest-plugin": "^3.1.1"
  }
}

1. Setting output.filename = '[name].bundle.js' + output.publicPath = '/dist/

OK

2. Setting output.filename = '[name].[contenthash].js' + output.publicPath = '/dist/

404 Error Response

3. Setting output.filename = '[name].[contenthash].js' + output.publicPath = 'auto'

OK

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

What is the expected behavior?

So, I realized
when I use webpack caching machenism such as output.filename = [contenthash].js, I cannot use output.publicPath option.
This happens both in 'development' mode and 'production' mode.

Exprected behavior is
even though the webpack users set output.filename with [contenthash],
webpack output must be adjusted according to the output.publicPath value.

Other relevant information:
webpack version: v5.45.1
Node.js version: v14.15.0
Operating System: ubuntu-20.04-LTS
Additional tools:

[alexander-akait]

Do not ignore this If the current behavior is a bug, please provide the steps to reproduce.

[OptimistLabyrinth]

yes it works fine but
when I set { output.filename = [name].bundle.js + output.publicPath = 'somefolder' } my app works fine
however when I set { output.filename = [name].[contenthash].js + output.publicPath = 'somefolder' } my app always responds with 404 and I was forced to set { output.publicPath = 'auto' }.
currently I haven't released any product so there's no problem
I was being cautious in case I happen to be in a situation where I need to use both output.filename = [contenthash].js setting and output.publicPath setting.

is it troublesome to edit this part ?

[alexander-akait]

I don't have problem with filename: '[name].[contenthash].js', in your example

[OptimistLabyrinth]

that's strange

[OptimistLabyrinth]

I'l look for another factor that bring about it happens. I think it would take time.
Would you close this disscussion or just leave open ?

[alexander-akait]

Let's keep open, it is just dicussion