Where are the VSCode error logs for extensions?

Question

When I get an extension error I have no way of knowing why the error happens.

score 152 · Answer 1 · answered Jan 26 '19 at 19:21

152

You're probably looking for:

cmd-shift-p -> Search Show Logs -> Extension Host

answered Jan 26 '19 at 19:21

Benno Straub

2,268
3
19
21

4

this should be the accepted answer, I was looking for these logs too – Luciano May 14 '20 at 13:42
2

unfortunately I get notification error when I click extension button, but there are no new logs – Ewoks Jul 14 '20 at 13:48
6

For me the best route was cmd-shift-p, then search Developer: Open Extension Logs Folder. – saswanb Sep 01 '20 at 20:57
4

If you're using remote development (e.g. over SSH), click on `Remote Extension Host` instead. – Jin Oct 29 '20 at 12:28

Mike Lischke · Accepted Answer · 2018-04-26T07:53:11.450

From what I know there are no dedicated logs for extensions. When you are debugging your extension you can write notes to the console. However, when you have problems with an installed extension this won't help. But keep in mind vscode is kinda "web browser", so it has the usual browser developer tools (see Help -> Developer Tools),

which will show you runtime errors (and all the other stuff those tools allow usually, including the entire vscode DOM). That's probably the best option you have in such a scenario.

And for extensions that use previewHTML (or web views) there's a similar goodie, but tailored towards HTML development. Use ctrl/cmd+shift+P to open the command pallet and type "Webview Tools". Select the match to open a similar view like the one described in the first paragraph. But this one is only for the previewHTML content and allows you to debug that! This view is only available when a page containing a web view/previewHTML is active and closes automatically when the web view tab is closed.

I don't think this helps too much. I had the similar situation (popup: "Kubectl command failed" without any further indication), and the Developer Tools of Chromium don't help. Most of the people will not develop extensions, but use them. So, no answer at all, I don't understand all the votes. — mliebelt, Jul 25 '20 at 08:25

score 14 · Answer 3 · answered Mar 09 '22 at 14:42

14

Another easy way is to select "Output" in the terminal window (open it from menu "Terminal" > "New Terminal" if it is not already open). Then, use the scrolling menu on the right side and select what you need.

answered Mar 09 '22 at 14:42

Pozinux

964
2
10
22

2

This seems like 100% the correct answer to me – wallacer Jun 24 '22 at 02:22
Are those stored in any file? The non extension logs are put into files: https://stackoverflow.com/questions/46373762/where-are-visual-studio-code-log-files but I can't see the non-extension ones there :-( It would be easier to browse files for large logs. – Ciro Santilli OurBigBook.com Mar 23 '23 at 11:21

Where are the VSCode error logs for extensions?

3 Answers3

Linked