Performance Metrics Issue with speed-measure-webpack-plugin and case-sensitive-paths-webpack-plugin

[yzh1699]

Hello speed-measure-webpack-plugin Team,

I'm encountering an issue where the integration of speed-measure-webpack-plugin (smp) with case-sensitive-paths-webpack-plugin seems to distort the performance metrics reported by smp.

Issue Description:
When running builds with both speed-measure-webpack-plugin and case-sensitive-paths-webpack-plugin, the metrics suggest a significant performance overhead associated with the case-sensitive plugin. However, after disabling case-sensitive-paths-webpack-plugin by commenting it out, I observed no meaningful change in the actual build times when using time npm run build to monitor the overall build time.

This leads me to believe that the interaction between these two plugins may be causing speed-measure-webpack-plugin to report inaccurate metrics.

Steps to Reproduce:

1. Install speed-measure-webpack-plugin (version 1.5.0) and case-sensitive-paths-webpack-plugin (version 2.3.0).
2. Integrate both plugins into your webpack configuration.
3. Run a build with time npm run build to get the baseline performance metrics.
4. Comment out the case-sensitive-paths-webpack-plugin integration using:

   // config.plugin('CaseSensitivePathsPlugin').use(CaseSensitivePathsPlugin)

5. Run the build again with time npm run build and compare the metrics.

Expected Behavior:
The performance metrics provided by speed-measure-webpack-plugin should accurately reflect the impact of each plugin on the build process.

Actual Behavior:
The reported metrics from speed-measure-webpack-plugin suggest a performance impact from case-sensitive-paths-webpack-plugin that does not correlate with the actual build times observed using time npm run build.

Additional Information:

• speed-measure-webpack-plugin version: 1.5.0
• case-sensitive-paths-webpack-plugin version: 2.3.0
• Operating System: Windows11 or macOS Monterey
• Node.js version: 14.21.3

I am concerned that this issue could lead to developers making misguided optimizations based on misleading metrics. I would appreciate any guidance you can provide and am willing to assist in diagnosing this problem further.

Thank you for your time and assistance.

Best,
Zehua YU