Mess when using Angular CLI

[Kenya-West]

I'm using webpack 4 (backend) and Angular CLI (frontend) in a single repo, and this is what I get when using concurrently:

When I use repos separately and without concurrently, Angular CLI doesn't spam like that.

[gustavohenke]

What's the concurrently version you're using?

[Kenya-West]

{
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.6.3",
    "@angular/cli": "6.0.3",
    "concurrently": "^3.5.1", // this
    "webpack": "^4.7.0",
    "webpack-cli": "^2.1.3",
    "webpack-watch-server": "^1.2.1"
  }
}

[cawalch]

Same issue here (webpack 4). Using raw fixes it, but at the loss of the prefix option.

[enricoreich]

Unfortunately same issue here with webpack 4.16.3 and concurrently 3.6.1 but without angular-cli on Windows cmd and powershell.

[kopach]

Unfortunately I do have a problem when using --raw option on Windows OS. If used with angular cli (e.g. ng serve or ng build, etc) it's getting stuck and command never gets executed. So, temporary workaround for me it's to add --no-progress to the ng command and do not use --raw option for concurrently.

[gustavohenke]

Hi folks, can any of you isolate the issue, please?
Also provide Node, npm and Windows versions so that I can run it locally and find a fix, unless you can submit a PR.

[kopach]

Issue seems not to be reproducible anymore in angular CLI 6.1.3. However it's reproducible in angular cli 6.0.0. Here is a project generated with angular cli v 6.0.0

In order to reproduce issue:

1. Clone repo
2. run npm install
3. run npm run start:concurrently