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

Webpack terminal output has no colour on Windows in 1.3.0-rc.3 #7239

Closed
davewragg opened this issue Aug 2, 2017 · 8 comments · Fixed by #7569
Closed

Webpack terminal output has no colour on Windows in 1.3.0-rc.3 #7239

davewragg opened this issue Aug 2, 2017 · 8 comments · Fixed by #7569
Assignees
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity5: regression type: bug/fix

Comments

@davewragg
Copy link

davewragg commented Aug 2, 2017

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Versions.

@angular/cli: 1.3.0-rc.3
node: 8.0.0
os: win32 x64
@angular/animations: 4.3.2
@angular/common: 4.3.2
@angular/compiler: 4.3.2
@angular/core: 4.3.2
@angular/forms: 4.3.2
@angular/platform-browser: 4.3.2
@angular/platform-browser-dynamic: 4.3.2
@angular/router: 4.3.2
@angular/service-worker: 1.0.0-beta.16
@angular/cli: 1.3.0-rc.3
@angular/compiler-cli: 4.3.2
@angular/language-service: 4.3.2
Windows 10, git bash (MINGW32)
git version 2.13.2.windows.1

Repro steps.

npm i -g @angular/cli@next
ng new test
cd test
ng build

The log given by the failure.

No error, but terminal output has no colouring.

Desired functionality.

Output has lovely colours on 1.2.6, how I long to see them again.

Mention any other details that might be useful.

Probably not the most important bug you'll see, but a bit of a shame.

@Brocco Brocco added P5 The team acknowledges the request but does not plan to address it, it remains open for discussion severity1: confusing labels Aug 17, 2017
@filipesilva
Copy link
Contributor

Does this still happen in 1.3.0 final?

@davewragg
Copy link
Author

Hi @filipesilva, I'm afraid so.

@filipesilva filipesilva added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent and removed P5 The team acknowledges the request but does not plan to address it, it remains open for discussion labels Aug 31, 2017
@filipesilva
Copy link
Contributor

I'm on windows and don't get this with the terminal I use (conemu/gitbash). What terminal do you use?

@davewragg
Copy link
Author

I'm on Git Bash (via Git Extensions/Git for Windows), just running from direct from start menu. I don't have conEmu on this machine. Just went and double checked - reverting to 1.2.6 (for example) produces coloured output, but from 1.3.0 (including rcs) the output is colourless. Can supply screenshots if useful?

@filipesilva
Copy link
Contributor

You see something like this, right? I just tried on gitbash without anything else and this is what I got.

image

@davewragg
Copy link
Author

Yep, exactly that. On 1.2.6 the webpack output had a bit of green and white in there.

@filipesilva
Copy link
Contributor

Got it, will investigate.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity5: regression type: bug/fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants