No Parsed/Gziped sizes if there is build hash in output path

[martinkadlec0]

Issue description

If there as build hash in webpack's output path, I get following error from WBA:
Error parsing bundle asset "/xxx/app/dist/[hash]/app.js": no such file.

My webpack output config:

	output: {
		filename: '[name].js',
		path: path.join(__dirname, './dist/[hash]/'),
		publicPath: `${cdnPublicPath}[hash]/`,
		chunkFilename: '[name].js',
	},

This causes that there is no gziped/parsed size on the WBA page.

Technical info

• Webpack Bundle Analyzer version: 3.3.2
• Webpack version: 4.35.0
• Node.js version: 10.13
• npm/yarn version: npm 6.9
• OS: Mac OS Mojave

Debug info

How do you use this module? As CLI utility or as plugin?
Plugin

If plugin, what options were provided? (e.g. new BundleAnalyzerPlugin({ analyzerMode: 'disabled', generateStatsFile: true }))
No options

What other Webpack plugins were used?
webpack.DefinePlugin
CircularDependencyPlugin
FlowStatusWebpackPlugin
ExtractCssChunks
HtmlWebpackPlugin
SpriteLoaderPlugin

Demo repo

https://github.com/martinkadlec0/wba-build-hash

[valscion]

Are you able to create a reproduction repository so that some contributor or us could check this error?

[martinkadlec0]

Sure, there you go https://github.com/martinkadlec0/wba-build-hash

[valscion]

Ah ok, now I get it! Thank you, the reproduction repository helped.

This does seem to be a lack of a feature that could also be categorized as a bug. The crux is this webpack config:

output: {
    filename: '[name].js',
    path: __dirname + '/dist/[hash]/',
  },

and that webpack-bundle-analyzer uses the path as-is instead of using some version where the [hash] would've been replaced with what it was in the end.

[valscion]

So the problem is here:

https://github.com/webpack-contrib/webpack-bundle-analyzer/blob/95d03b70d5180076813867ee78c3127810b8e94b/src/BundleAnalyzerPlugin.js#L137-L138

The issue is not present when generating stats JSON separately and using the CLI to open the reporter:

So we should figure out a way to get the bundle directory location from somewhere else than compiler.outputPath as that path has not been expanded by webpack. Hmm...