simple-progress-webpack-plugin icon indicating copy to clipboard operation
simple-progress-webpack-plugin copied to clipboard

Plugin prints (partial) duplicate information

Open mjansen-dc opened this issue 4 years ago • 2 comments

Problem In all progress formats, the "Webpack: Starting ..." is printed again at the tail end of the compilation. With some formats this causes the entire output to be repeated.

Minimal format:

$ webpack
Finished after 0.142 seconds.

Finished after 0.001 seconds.

asset main.js 1.18 KiB [emitted] (name: main)
./src/index.js 1 bytes [built] [code generated]
webpack 5.40.0 compiled successfully in 138 ms
Done in 0.79s.

Compact format:

$ webpack
Webpack: Starting ...

  √ Compile modules
  √ Build modules
  √ Optimize modules
  √ Emit files

Finished after 0.164 seconds.

Webpack: Starting ...

  √ Compile modules
  √ Build modules
  √ Optimize modules
  √ Emit files

Finished after 0.000 seconds.

asset main.js 1.18 KiB [compared for emit] (name: main)
./src/index.js 1 bytes [built] [code generated]
webpack 5.40.0 compiled successfully in 160 ms
Done in 0.81s.

Expanded format: Note: I removed most of the output of progress logs here for issue clarity You might also notice some weirdness in this and verbose logging, I will make a separate ticket describing this

$ webpack
Webpack: Starting ...

  > Compile modules

  > Build modules

  > Optimize modules
    → [-2%] Sealing ...
    → [102%] Sealing ...

  > Emit files

Finished after 0.123 seconds.

Webpack: Starting ...

  > Emit files

Finished after 0.000 seconds.

asset main.js 1.18 KiB [compared for emit] (name: main)
./src/index.js 1 bytes [built] [code generated]
webpack 5.40.0 compiled successfully in 123 ms
Done in 0.75s.

Verbose format: Note: I removed most of the output of progress logs here for issue clarity

$ webpack
[12:40:08] Webpack: Starting ...

[12:40:08] Webpack (0%) - Compile modules
[12:40:08] Webpack (9%) - Compile modules
[12:40:08] Webpack (10%) - Build modules
[12:40:08] Webpack (70%) - Build modules
[12:40:08] Webpack (71%) - Optimize modules (sealing)
[12:40:08] Webpack (94%) - Optimize modules (sealing)
[12:40:08] Webpack (95%) - Emit files
[12:40:08] Webpack (99%) - Emit files

[12:40:08] Finished after 0.154 seconds.

[12:40:08] Webpack: Starting ...

[12:40:08] Webpack (99%) - Emit files
[12:40:08] Webpack (99%) - Emit files
[12:40:08] Webpack (99%) - Emit files

[12:40:08] Finished after 0.001 seconds.

asset main.js 1.18 KiB [compared for emit] (name: main)
./src/index.js 1 bytes [built] [code generated]
webpack 5.40.0 compiled successfully in 150 ms
Done in 0.78s.

Environment Operating System: Windows 10 Node version: 12.13.0 Webpack version: 5.40.0 Plugin version: 2.0.0

Webpack config: Note: the mode setting does not affect this. I simply added this to suppress the log which asks you to set it, for the rest its a minimal zero config webpack config

const SimpleProgressWebpackPlugin = require("simple-progress-webpack-plugin");

module.exports = {
  mode: "development",
  plugins: [
    new SimpleProgressWebpackPlugin({
      format: "compact",
    }),
  ],
};

mjansen-dc avatar Jun 25 '21 10:06 mjansen-dc

I got the exact same problem. I've try while removing all other plugins to prevent any collision but I still get 2 Webpack log.

jimblue avatar Sep 28 '21 21:09 jimblue

Still same problem here.

jrson83 avatar Jan 25 '22 14:01 jrson83