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

Logging with --no-colors outputting objects #48

Closed
wants to merge 1 commit into from

Conversation

jakub-g
Copy link
Collaborator

@jakub-g jakub-g commented Jul 10, 2013

colors.js hasn't been updated in npm for a long time but it's being updated on Github.

The issue here was that when logging from Attester with --no-colors passed in command line, it sometimes logged the String object (console.dir fashion) instead of a logging a string literal (precisely it was fixed by Marak/colors.js@5ca667d).

@piuccio
Copy link
Contributor

piuccio commented Jul 11, 2013

Instead of pointing to our forks, isn't it better if we ask developers to publish a new version on npm?

@jakub-g
Copy link
Collaborator Author

jakub-g commented Jul 11, 2013

Yep in the ideal world it'll be better, but with using forks we are not blocked by other people. We can update our deps back to point to npm as soon as the new versions are released.

Asked here: Marak/colors.js#36

The issue here was that when logging from Attester with `--no-colors`
passed in command line, it sometimes logged the String object (console.dir
fashion) instead of a logging a string literal (precisely it was fixed by
Marak/colors.js@5ca667d).

Close attester#48.
@jakub-g
Copy link
Collaborator Author

jakub-g commented Jul 29, 2013

0.6.1 has been released in npm, I checked it and it looks fine

@jakub-g jakub-g closed this in ccd5c26 Jul 29, 2013
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

Successfully merging this pull request may close these issues.

2 participants