HtmlWebpackPlugin.publicPath resolves incorrectly

[jlurena]

Current behaviour 💣

HtmlWebpackPlugin.publicPath resolves to ${output.path}/${output.publicPath} instead of output.publicPath

Expected behaviour ☀️

HtmlWebpackPlugin.publicPath should resolve to output.publicPath

Reproduction Example 👾

const HtmlWebpackPlugin = require('html-webpack-plugin');
const path = require('path');

module.exports = {
  context: __dirname,
  entry:  path.resolve(__dirname, './src/index.jsx'),
  output: {
    path:       path.resolve(__dirname, 'public'),
    publicPath: '/assets',
    filename:   'assets/[contenthash:8].js'
  },
  plugins: [
    new HtmlWebpackPlugin({
      filename:   'index.html'
    })
  ],
  module: {
    rules: [
      {
        test:    /\.jsx?$/,
        exclude: /node_modules/,
        use:     ['babel-loader']
      }
    ]
  },
  resolve: {
    extensions: ['.js', '.jsx']
  }
};

Above configuration would create index.html at public/ directory and script paths would be loaded as /assets/assets/123abc.js

Environment 🖥

$ node -e "var os=require('os');console.log('Node.js ' + process.version + '\n' + os.platform() + ' ' + os.release())"
Node.js v12.16.1
darwin 20.3.0

$ npm --version
7.8.0

$ npm ls webpack
jlurena.me@1.0 /Users/jean/Projects/jlurena.me
├─┬ css-loader@5.2.1
│ └── webpack@5.30.0 deduped
└── webpack@5.30.0

$ npm ls html-webpack-plugin
jlurena.me@1.0 /Users/jean/Projects/jlurena.me
└── html-webpack-plugin@5.3.1

Workaround for above so far is to set HtmlWebpackPlugin.publicPath = '/'

[jantimon]

/assets/assets/123abc.js is the correct path as it uses publicPath + filename

[jlurena]

/assets/assets/123abc.js is the correct path as it uses publicPath + filename

abc123.js lives in /assets, not /assets/assets, so it is still incorrect

In addition, filename is abc123.js not assets/abc123.js

[stale]

This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days.