Issue description
There are 2 issues for the plugin code(not bin/analyzer). Currently, it is not a bug but nice to have
BundleAnalyzerPlugin.js should use InfrastructureLogger from webpack compiler. When I run my jest test, there are some noise message from the plugin. See the following screenshot.

I can silent the console.log for my jest test. But I have to write some to find the plugin in my shared webpack.config.js and then replace the existing plugin with another one to silent log messages.
- When I launch the webpack-dev-server, I expect my
dist should be empty. Currently it always has report.html. Other assets are in memfs. I have a jest test to check the folder is empty. Now I have to write more code to handle it differently

Issue description
There are 2 issues for the plugin code(not bin/analyzer). Currently, it is not a bug but nice to have
BundleAnalyzerPlugin.jsshould use InfrastructureLogger from webpack compiler. When I run my jest test, there are some noise message from the plugin. See the following screenshot.I can silent the
console.logfor my jest test. But I have to write some to find the plugin in my sharedwebpack.config.jsand then replace the existing plugin with another one to silent log messages.distshould be empty. Currently it always has report.html. Other assets are in memfs. I have a jest test to check the folder is empty. Now I have to write more code to handle it differently