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

Color enforcement #2068

Closed
ArmorDarks opened this issue Sep 8, 2016 · 2 comments
Closed

Color enforcement #2068

ArmorDarks opened this issue Sep 8, 2016 · 2 comments

Comments

@ArmorDarks
Copy link

We've encountered an issue during spawning processes with JSPM 0.17-beta. For example, if try to use grunt-shell JSPM output ends up completely mono-coloric:

conemu_2016-09-08_14-46-37

After reading sindresorhus/grunt-shell#21 and this topic, if I'm not mistaken, it seems that the only way to bypass this issue is to enforce color with --color flag.

As far as I know, JSPM doesn't support --color flag. At least, I didn't find it in docs. But, strangly enough it works:

sublime_text_2016-09-08_14-47-25

But for some reason it thinks that --color isn't a flag, but output directory:

conemu_2016-09-08_14-48-24

I then tried to specify output file explicitly, but JSPM simply concatenating both path into single wrong path, resulting in error:

sublime_text_2016-09-08_14-50-21

'jspm build "source/scripts/main.js" "test.js"', without --color works as expected, but, once again, no color in piped through grunt-shell output:

sublime_text_2016-09-08_14-55-17

I'm quite confused. Am I missing something, or JSPM indeed mistakenly takes flag for output path? Is there a support of --color in JSPM?

@dinoboff
Copy link

dinoboff commented Sep 8, 2016

A "--color" flag would be nice but you could use child_process package directly and set stdio to "inherit". E.g.:

const ps = require('child_process');

ps.execSync('jspm inspect', {stdio: 'inherit'});

@ArmorDarks
Copy link
Author

Thanks for reply!

Hm, I'm not sure, but it seems to be impossible to control that parameter via grunt-shell.

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

No branches or pull requests

3 participants