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

TypeScript, mocha, chalk doesn't output color to debug console? #4755

Closed
ghost opened this issue Mar 29, 2016 · 7 comments
Closed

TypeScript, mocha, chalk doesn't output color to debug console? #4755

ghost opened this issue Mar 29, 2016 · 7 comments
Assignees
Labels
verified Verification succeeded

Comments

@ghost
Copy link

ghost commented Mar 29, 2016

In my 0.10.11 version, chalk console logging using chalk works. In the 0.10.12-insider version it doesn't.

  • VSCode Version: 0.10.12-insider
  • OS Version: Windows 10
  • Language: TypeScript 1.8.9, Node 4.1.1, Mocha 2.3.4,
  • Launch:
        {
            "name": "[WP] test",
            "type": "node",
            "request": "launch",
            "program": "${workspaceRoot}/node_modules/mocha/bin/_mocha",
            "stopOnEntry": false,
            "args": [
                "test.bundle.js",
                "--no-timeouts",
                "--max_old_space_size=2048",
                "--colors"
            ],
            "cwd": "${workspaceRoot}/bin-webpack/test",
            "runtimeExecutable": null,
            "runtimeArgs": [],
            "env": {},
            "sourceMaps": true,
            "outDir": "${workspaceRoot}/bin-webpack/test"
        },

Steps to Reproduce:

  1. import chalk = require('chalk');
  2. console.log(chalk.magenta('some text'));
@ghost
Copy link
Author

ghost commented Mar 29, 2016

lost coloring

@Tyriar
Copy link
Member

Tyriar commented Mar 29, 2016

Duplicate of #571

@Tyriar Tyriar closed this as completed Mar 29, 2016
@ghost
Copy link
Author

ghost commented Mar 29, 2016

Hi @Tyriar! I appreciate the quick response. Does that really apply if it works in 0.10.11 already but does not work in the 0.10.12-insiders version?

@Tyriar
Copy link
Member

Tyriar commented Mar 29, 2016

@bill-mybiz oh sorry, misread, didn't think it was a regression?

@Tyriar Tyriar reopened this Mar 29, 2016
@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug tasks Task system issues labels Mar 29, 2016
@ghost
Copy link
Author

ghost commented Mar 29, 2016

@Tyriar Yeah I think I would consider it a regression, but I'm not sure if it would be a regression in VS Code per se or if it's something that breaks chalk and possibly others. I just know that for tracing asynchronous code, the console coloring has been a Godsend as I'm able to match interspersed log entries extremely efficiently.

@dbaeumer
Copy link
Member

@bpasero I think this is the output window.

@dbaeumer dbaeumer removed the tasks Task system issues label Mar 30, 2016
@dbaeumer dbaeumer assigned bpasero and unassigned dbaeumer Mar 30, 2016
@bpasero
Copy link
Member

bpasero commented Mar 30, 2016

#4616

@bpasero bpasero closed this as completed Mar 30, 2016
@bpasero bpasero removed the bug Issue identified by VS Code Team member as probable bug label Mar 30, 2016
@bpasero bpasero added the verified Verification succeeded label Apr 29, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants