CODEWITHSUNDEEP
javascriptvisual-studio-codevscode-extensions
Harsh Prakash Agarwal
Harsh Prakash Agarwal

Reputation: 351

I do not see the hello world command in command pallete

So the tutorial to developing visual studio code extensions says to hit F5 and then command palette which is where I should see the hello world command given by this default code for extension. This is the repository for the default code generated by following the tutorial. I do not see the command and I require some help as to troubleshoot. Let me know if any additional info is required.

Upvotes: 4

Views: 1316

Answers (5)

Pratik Katte
Pratik Katte

Reputation: 1

Check the version of vscode in package.json. It should match the vscode application version you are running.

 "engines": {
    "vscode": "^1.92.0"   
  },

Upvotes: 0

Thomas M K
Thomas M K

Reputation: 86

I had the same problem and when I go to help there I see restart to update. I just clicked on that tab and vs code restarted. After that I'm able to see the Hello World in command palette.

So try updating your VS Code or check help tab is there any updation required.

Upvotes: 1

Josh Majors
Josh Majors

Reputation: 11

I had the same issue, but fixed it by updating VSCode. I'm on Ubuntu and have VSCode installed via snap. I had to make sure all VSCode processes were closed then ran the command snap refresh code.

Upvotes: 0

Bill Brotherton
Bill Brotherton

Reputation: 56

I had the same problem and found that the extensions required VsCode 1.74. Check the Log(Window) in the 'Extension Development Host`.

Upvotes: 4

Kamen Minkov
Kamen Minkov

Reputation: 3712

During development the extension will only live in the "guest" window that appears when you start debugging - this is where you should be looking for the contributed command (or anything else done by the extension).

The extension will appear in your VSCode instance if you install it - either by packaging it and installing it locally or by publishing it to the Extension Marketplace and then installing it from there.

Edit: I pulled your repo and ran the extension. Everything is working as expected. You're probably missing something.

Upvotes: 1

Related Questions