-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Task runner colors #9
Comments
@mjosh954 @madskristensen The problem is that the npm CLI doesn't offer a I'm thinking that one of these modules would need to be installed locally with the NPM Scripts Task Runner extension. Not sure how involved that is or if it's even possible to do with an extension. |
Colors would be nice. We can ship the needed node modules with this extension. How would chalk/cli-color work with npm scripts? How do you hook it up? I believe the missing colors is a Windows only issue and the real fix might be in sending a PR to npm to fix it |
I've found a much simpler way to accomplish this which doesn't require any additional dependencies. Look for a PR either later tonight or early tomorrow. |
PR submitted. Apparently, it is possible to set color via the CLI. It just isn't explicitly documented. |
doesn't look like the colors are working when using latest node version. any ideas of how to get colors working when using latest node version in NPM Task Runner? thanks! |
@scottaddie I repro the issue but can't find a workaround. Any ideas? |
@madskristensen Are you using Node v4 or v6? |
.NET Core Preview 1 tooling has node v5 |
i'm using latest stable, which is v6 |
I think this is either not fixed, or the NpmTaskRunner notes need to be updated. Using: Colors display in a command window but do not display in NpmTaskRunner. |
Colors are being shown when running the update task. This is very strange... |
Any progress on this? I'm using the task runner to run some Mocha tests and they look oh so boring without the red crosses and green tickets that I usually see! |
@Yerkon Can you please provide your Windows, Visual Studio, npm, and Node versions? I ask because some users do see color, including myself. I'm trying to pin down the problematic component(s). |
@scottaddie My configuration:
|
Updated:
|
No color here either If I have the yarn.lock file, it runs yarn instead of npm and that has no color either. I have color for yarn or npm from normal command line of course. |
Same for me. No colors in NPM Task Runner in Visual Studio (e.g. npm start) Wierd thing is "npm update" works with colors: Both started from within NPM Task Runner in Visual Studio of course (normal command line has colors). So the suspicious part which makes it fail is maybee the "run" parameter? Node v6.11.4 |
You can just run the start command without the word run to confirm your
suspicion.
…On Nov 22, 2017 4:58 AM, "jingel81" ***@***.***> wrote:
Same for me.
No colors in NPM Task Runner in Visual Studio (e.g. npm start)
cmd.exe /c npm run start --color=always
Wierd thing is "npm update" works with colors:
cmd.exe /c npm update --color=always
Both started from within NPM Task Runner in Visual Studio of course
(normal command line has colors).
So the suspicious part which makes it fail is maybee the "run" parameter?
Node v6.11.4
NPM 3.10.10
Visual Studio 2017 (15.4.4)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJE-3WM1jDdDGhQLMvSAz37vyGHTCloYks5s4_BJgaJpZM4G6w1q>
.
|
Is there a way for the Task Runner Explorer output to also display colors like the Gulp Task Runner does? I started to convert most of my gulp tasks in to npm commands and when I run a eslint from my gulp task runner, it comes all colored. However, when I run the same command from npm, it's standard b/w.
The text was updated successfully, but these errors were encountered: