This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
Add logging using vscode-debug-logger #753
Merged
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
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.
Spun out my debug adapter logging in node2/chrome into a new node module: https://github.com/roblourens/vscode-debug-logger.
This adds a new launch config property, 'trace'. When it isn't set, there is no change, except that the calls to
logErrorwill be shown as errors in the console.When it's set to
true, all log messages will be written to a file, and the path to the file will be printed at the top of the console.When it's set to
"verbose", all log messages will be written to the file, and printed in the console.There's quite a lot of info printed, it should be enough to trace what happens when someone reports an error.