-
Notifications
You must be signed in to change notification settings - Fork 57
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
Colors not working with Mocha 2.4 anymore #129
Comments
Ok, with the latest Mocha fixes, Mochify stopped working completely. I'm going to nail the dependency to |
Related issue on Mocha repo: mochajs/mocha#2080 |
We replaced the custom colors with chalk since people were complaining about it for years. because chalk uses ie8 incompatible code it was stubbed out. However I now realize that consuming mocha on the command line via phantomjs will cause it to be stubbed as well. The solution is then to not stub chalk but instead polyfill some es5 stuff. I'll do this tomorrow. |
Have sympathy for trying to support old node, old browsers, and browsers that run in terminals all at once... |
Cool, thanks! 👍 |
@mantoni Even when mocha start working the colors on windows will not show up: https://twitter.com/gyandeeps/status/692355912233787393 because of how |
@gyandeeps We can probably work in some hack to make chalk output color in windows. If it worked before, we can make it work again. However, if you're using phantomjs at this point, you're SOL. I'll be on this in a few. |
@boneskull Sure. Let me know if you need some help with it. |
@gyandeeps Thanks for sharing. I know about the issues with stdio in the Cygwin context. It's a never ending source of fun for me at work. Mochify detects color using the |
|
Didn't try git bash yet. We're using npm scripts in cygwin / mintty and that works fine. |
Even the travisci build dont show color anymore. |
@gyandeeps You're talking about Mocha now. Mochify is a slightly different story. You're not testing eslint in the browser with Mochify, do you? 😀 |
Nope. I was on the convo of using |
please see mochajs/mocha#2080 for status and further info |
Issue fixed in Mocha Happy testing! |
mocha: ^2.3.4 to ^2.4.5 mochify: ^2.15.0 to ^2.17.0 There's an intermediate version of mocha (>2.4.0, <2.4.5) that broke compatability with PhantomJS by its use of a particular color output library, documented here: mantoni/mochify.js#129 Bumping to this version ensures we're past that bug, which is fixed in 2.4.5 (https://github.com/mochajs/mocha/blob/master/CHANGELOG.md#245--2016-01-28)
I saw a few commits and releases around chalk in Mocha. Maybe @boneskull can help shed some light on the issue?
The text was updated successfully, but these errors were encountered: