Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confusing output when running two builds concurrently #68

Open
OliverJAsh opened this issue Jun 3, 2020 · 1 comment
Open

Confusing output when running two builds concurrently #68

OliverJAsh opened this issue Jun 3, 2020 · 1 comment

Comments

@OliverJAsh
Copy link

OliverJAsh commented Jun 3, 2020

Version

v4.0.0

Reproduction link

https://github.com/OliverJAsh/webpack-concurrently/tree/bar

Steps to reproduce

Reduced test case: https://github.com/OliverJAsh/webpack-concurrently/tree/bar

Note: you must use the bar branch.

Run yarn and then npm run compile.

We are running two webpack builds concurrently. Each webpack build has its own instance of the WebpackBar plugin, with a unique name (client and server).

What is actually happening?

  • We see two bars, but a single bar will flicker between client and server.
  • One of the bars never updates.

Screen Recording 2020-06-03 at 13 35 04

What is expected ?

I would not expect this flickering—each build should have its own bar and it should not interfere with other bar instances.

This bug report is available on Nuxt community (#c44)
@ghost ghost added the cmty:bug-report label Jun 3, 2020
@joacub
Copy link

joacub commented Nov 30, 2020

same here, concurrently seems works only in the same nom run command, concurrently seems not work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants