unjs / webpackbar

Elegant ProgressBar and Profiler for Webpack 3 , 4 and 5
MIT License
2.07k stars 66 forks source link

timing report difference #118

Open grosfaignan opened 1 year ago

grosfaignan commented 1 year ago

Environment

webpack -v

  System:
    OS: Windows 10 10.0.19044
    CPU: (4) x64 Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
    Memory: 6.07 GB / 15.91 GB
  Binaries:
    Node: 14.17.5 - C:\Program Files\nodejs\node.EXE
    npm: 6.14.14 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (112.0.1722.46)
    Internet Explorer: 11.0.19041.1566
  Packages:
    babel-loader: ^9.1.2 => 9.1.2
    css-loader: ^6.7.3 => 6.7.3
    eslint-webpack-plugin: ^4.0.0 => 4.0.0
    html-webpack-plugin: ^5.5.0 => 5.5.0
    less-loader: ^11.1.0 => 11.1.0
    postcss-loader: ^7.1.0 => 7.1.0
    style-loader: ^3.3.2 => 3.3.2
    terser-webpack-plugin: ^5.3.7 => 5.3.7
    time-analytics-webpack-plugin: ^0.1.20 => 0.1.20
    webpack: ^5.76.3 => 5.76.3
    webpack-bundle-analyzer: ^4.8.0 => 4.8.0
    webpack-cli: ^5.0.1 => 5.0.1
    webpackbar: ^5.0.2 => 5.0.2

Reproduction

const { TimeAnalyticsPlugin } = require("time-analytics-webpack-plugin");
const WebpackBar = require('webpackbar');

let config = {
  //***
  plugins: [
    new WebpackBar({
      reporters:['fancy','profile'],
      profile:true,
    }),
  ],
  //***
}
const wrappedConfig = TimeAnalyticsPlugin.wrap(config);
module.exports = wrappedConfig;

Describe the bug

TimeAnalyticsPlugin and WebpackBar produce différents timing reports results.

Additional context

No response

Logs

No response