gulp build: when gulp-jscs fails, its error message is unreadable in Windows command prompt

[UltCombo]

The issue seems to be specific to Windows.

Steps to reproduce:

1. Use the (currently experimental) gulpfile branch
2. Create a new project
3. Edit a .js file in order for jscs to fail
4. Run gulp build

gulp-jscs's error message in Windows 7's cmd.exe only has line breaks visible:

However, actually, it looks like the issue is with gulp-jscs's coloring -- if one copies/inspects the actual stdout contents, the correct error message is there.

The same bug also appears in Git Bash:

The error message is at least visible in Console2 (albeit the coloring is not applied):

Noting again: the issue is apparently specific to Windows; The error message is correctly colored in OS X 10.10's zsh.

[UltCombo]

I believe this should be fixed when gulp-jscs supports reporters, though. For reference:

• Implement configurable reporters jscs-dev/gulp-jscs#39
• Support custom reporters (and reporters from jscs) jscs-dev/gulp-jscs#41
• Reporter output in Windows jscs-dev/gulp-jscs#48
• Attach jscs errors to the file object, like gulp-jshint. jscs-dev/gulp-jscs#57

[UltCombo]

Well, coloring is not that important, so I guess we can workaround this issue by disabling gulp-jscs coloring in Windows for the time being, until gulp-jscs supports proper reporters.

[jaydson]

I'm late.
So, the issue was fixed?

[UltCombo]

Yep. ;) I'm updating some details and writing docs for the gulp version, soon I'll push a slush-es6 alpha release. Will make a couple more tests to make sure everything is alright.

[jaydson]

👍

[UltCombo]

Pushed an alpha release! You can try it with:

npm i -g slush-es6@alpha

Let's push a stable release after applying this workflow in Harmonic and giving it some road test.

[btormey]

Noticing this issue again on Windows 10

[UltCombo]

@btormey are you using the version 2.0.3? I'm pretty sure it was fixed in this version.

The next version will be a major release that replaces JSHint and JSCS with ESLint, though I'm currently pondering whether to add JSCS back now that it is able to lint all valid Babel code. By that point we should also have the ability to disable plugins via build.js, so you can use just what you want.

[btormey]

@UltCombo Ah, that is the issue, I've got 2.0.0 installed. Sorry, it's late here.

[UltCombo]

No problem, glad to help. 😄