fix: removing "Tracing..." console logging #853
Closed
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
Unnecessary logging that clutters the console and makes it harder to spot the real issues you might have. For example, we have ~200 modules in our project, meaning we get ~200 lines of log every time the bundles are regenerated, which happens every time you change a file (triggered by `gulp.watch`).
|
|
|
I wouldnt remove it as its sometimes quite useful. Instead this logs should be configurable via aurelia.json |
|
Ok, I can probably fix that. Out of curiosity, what is the use case for when you need that logging? Only for debugging purposes? |
|
Yep solely debugging, like figuring out where it stops or what parts are missing and not properly traced |
|
@genne I like the idea of being able to configure the output of |
|
@JeroenVinke this one can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Unnecessary logging that clutters the console and makes it harder to spot the real issues you might have.
For example, we have ~200 modules in our project, meaning we get ~200 lines of log every time the bundles are regenerated, which happens every time you change a file (triggered by
gulp.watch).