-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
Question: Logging in Extensions #44212
Comments
Doesnt |
Yes. Is there a recommended path for extension authors? |
cc @joaomoreno @sandy081 on logging |
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines. Happy Coding! |
@jpoon I can't support You should be able to configure one of those logging libraries to use console.log instead of something like |
Issue Type
Question
Description
Is it possible to leverage a node logging library as an Extension developer?
Particularly, I tried using Winston, Bunyan, and Debug, but wasn't able to see any output in console (from the developer tools).
I suspect it is due to this: #19750, but
"outputCapture": "std"
isn't a supported attribute inlaunch.json
for"type": "extensionHost"
.Is there an established best-practice for logging in extensions?
VS Code Info
VS Code version: Code 1.20.1 (f88bbf9, 2018-02-13T15:23:28.607Z)
OS version: Darwin x64 17.4.0
The text was updated successfully, but these errors were encountered: