nyan-progress-webpack-plugin

nyan-progress-webpack-plugin copied to clipboard

As you can see, there seems to exist a condition where multiple fast initial messages creates multiple partial Nyans before the one that ends up working/tracking the whole progress.

I'm on v1.0.3 and my dev server config is:

devServer: {
  quiet: false,
  noInfo: false,
  stats: {
    assets: false,
    colors: true,
    version: false,
    hash: false,
    timings: false,
    chunks: false,
    chunkModules: false
  }
},

Awesome plugin, by the way! :grin:

Yeah, that's because you have some console output occurred during progress (that "Child" line, I believe). I don't know is there a way to track what was printed in console from outside the plugin (probably there's no way).

Actually, I just checked ASCII escape codes - there is a "Save/restore cursor position" command, which could help (they say it's not widely supported by terminals though).

Another way to solve it (kinda) is to print nyan cat with a left offset, so that it's not overlapping other messages.

@mathieumg btw what terminal and font are you using? Your cat looks more like Cheshire cat :)

@mathieumg check out a new version, should be fixed now.

Actually that made it worse. :(

I wish I could screencap it, the behaviour is pretty spectacular on 1.1 haha. :stuck_out_tongue:

Do you want me to setup a toy project to reproduce the issue?

I'm using Ubuntu Mono and Bash on my home PC (the screenshots so far), I'll try with whatever I have at work tomorrow.

Thanks for the quick reaction by the way!

@mathieumg try to turn off webpack.ProgressPlugin if you have it, they are not supposed to be used together (should mention it in README probably).

I have the same behavior (Nyan scrolling down and leaving trails) even without --progress. I also still get the two initial partial Nyans (screenshot in OP), but on 1.0 the progress + Nyan were working correctly after that.

Hmm. Can you make an example project then?

Yeah, I'll try to do that!

@mathieumg just reproduced the issue - it happens when console output doesn't fit screen height. Will try to fix that.

Cool! Sorry for being slow on this, I've been held up with school as of late. :x

Should be better now

@mathieumg can you check it, so I can close this issue?

I think I had and there were still issues, but I wanted to revalidate. I'll try to recheck that ASAP.

Turned out I forgot that I'm using non-standard terminal :) Seems like default terminal in MacOS doesn't support restoring/saving cursor position, so I had to disable that feature by default.