This repository has been archived by the owner on Apr 13, 2024. It is now read-only.
On Node, send console.foo() logging to a file, or discard it #62
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This will be used for redirecting console.log() and friends to a file, when running in Node.
On Node, having this console output appear inline makes it difficult to check that normal output is correct, and also looks confusing for non-developers. Instead, intercept calls to `console.foo()`, and either write the logs to a file as indicated by `--log=FILE`, or discard them. Logging can still be followed easily by running `tail -f FILE` in a separate terminal. For now, all kinds of logs are sent to the same file. If necessary in future, we could direct different types to different files.
|
This brings #26 closer to imminent priority I think |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Node, having this console output appear inline makes it difficult to check that normal output is correct, and also looks confusing for non-developers. Instead, intercept calls to
console.foo(), and either write the logs to a file as indicated by--log=FILE, or discard them. Logging can still be followed easily by runningtail -f FILEin a separate terminal.For now, all kinds of logs are sent to the same file. If necessary in future, we could direct different types to different files.