-
Notifications
You must be signed in to change notification settings - Fork 445
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
Version release? #43
Comments
Yes. I keep getting |
+1 |
+1 Are you still supporting "colors" or not? If not could you please tell so maybe someone else can take care of it? |
Kind request to @Marak to publish a new release. |
+16 |
I'm on it. Have been away from real internet for awhile. On Thu, Mar 28, 2013 at 1:43 AM, Ron Korving notifications@github.comwrote:
|
👍 nice! |
@Marak thanks for your work. We all appreciate your effort! Look forward to the new release 👍 |
Thanks a lot! Looking forward to it :) |
Still looking forward to it :) |
I was about to ask for a new release, too. colors.mode='none' is causing my strings to break apart (fixed in 5ca667d but not yet released). |
It has been over a month since this has been requested. Please, either publish or give the ownership of the module to someone which will be a bit more proactive on the maintenance. I dont mean to be rude, but all that is asked here is to do npm publish, really. |
+1 |
Version |
A bug in colors.mode='none' was fixed upstream in: Marak/colors.js@5ca667d but the maintainer of colors has gone AWOL (see Marak/colors.js#43) and we don't yet have a released fix. Work around the bug by manually coercing the results of all naked color getters to a string. Change-Id: I4b0559f0dcba766168d13363b771f56b45e3b34c
Project: mediawiki/extensions/Parsoid 386195fa11f0fe097623280c03e043185c9accb0 Work around bug in colors package when using --no-colors option. A bug in colors.mode='none' was fixed upstream in: Marak/colors.js@5ca667d but the maintainer of colors has gone AWOL (see Marak/colors.js#43) and we don't yet have a released fix. Work around the bug by manually coercing the results of all naked color getters to a string. Change-Id: I4b0559f0dcba766168d13363b771f56b45e3b34c
The last release of this was a year ago, and quite a few important fixes have since been made. Could we get a new version released?
The text was updated successfully, but these errors were encountered: