Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

VSCode on Mac missing SFDX commands and menu items

See original GitHub issue

Following https://trailhead.salesforce.com/content/learn/projects/quick-start-lightning-web-components

Working on a Mac and there are some deviations in my experience compared to the instructions.

Summary

Only 3 SFDX commands in VS Code Command Palette. No SFDX options in context menu (right click)

Steps To Reproduce:

Installed Salesforce CLI : sfdx-cli/7.8.1-8f830784cc darwin-x64 node-v10.15.3
Installed Java SKD 11
Installed Visual Code (both standard and Insider) Version 1.36.0-insider (1.36.0-insider)
Installed Salesforce Extension Pack 46.4.0 and dependencies, included recommended
Checked running extensions, includes Lightning Web Components
Created Trailhead playground, reset password, authorised Org
Created new Project ‘HelloWorldLightningWebComponent’ (also tried new Project with Manifest)
Saved locally to a folder
Project includes folder structure including LWC folder

Expected result

Should have full suite of SFDX commands in the VS Code Command Palette Should have multiple SFDX options on context menu (right click)

Actual result

Typing SFDX into Command Palette only shows 3 options: Create and Set Up Project for ISV Debugging Create Project with Manifest Create Project
Therefore, unable to e.g. create Lightning Web Component as per Trailhead.
Can create via Terminal (right click lwc folder in sidebar, open terminal, paste command: sfdx force:lightning:component:create --type lwc -n helloWorld
Next step should be to deploy to Trailhead playground by right clicking the ‘default’ folder and clicking ‘SFDX: Deploy Source to Org’ - however there are no SFDX options on the right click (context menu)

Additional information

Feel free to attach a screenshot. Screen Shot 2019-07-04 at 11 06 11 am

VS Code Version: Version 1.36.0-insider (1.36.0-insider) SFDX CLI Version: sfdx-cli/7.8.1-8f830784cc darwin-x64 node-v10.15.3 OS and version: macIS Mojave 10.14.5 (18F132)

Issue Analytics

State:
Created 4 years ago
Comments:11 (4 by maintainers)

Top GitHub Comments

1reaction

lcamposcommented, Jul 9, 2019

@foweyboy can you clarify if you’ve authenticated to an org and set it as your project’s default ? This can be done by running SFDX: Authorize an Org, SFDX: Create a Default Scratch Org ... or using the org picker feature (bottom left footer) to pick a previously authenticated org.

Assuming you’ve done this, there is a current issue where this does happen and one of the workarounds is the one mentioned by @alexkadis. We have a fix for that scenario coming out this week (PR #1456 ).

0reactions

dbwelchcommented, Jul 19, 2021

Sme here, Mac user.

Top Results From Across the Web

VS Code Mac not Using SFDX Commands

1 Answer 1 · Show Hidden Files in Finder (could have removed the folders for the extensions in iterm, but decided to use...

Troubleshooting Common Issues | Salesforce for VSCode

If you don't see any SFDX commands in the command palette, make sure that you're working on a Salesforce DX project and that...

Salesforce CLI and Visual Studio Code Command Palette

In Visual Studio code, open the Command Palette by pressing Ctrl+Shift+P on Windows or Cmd+Shift+P on macOS. Type SFDX . Select SFDX: Authorize ......

Lesser Known VSCode Tips for Salesforce Developers

More Code, Less Work.Whether you are a beginner or an advanced developer, smart tips, and sharp tools can significantly improve your ...

Command Palette | Visual Studio Code Extension API

It's important that your command names are labeled appropriately so users can easily find them. ✔️ Do. Add keyboard shortcuts where appropriate; Use...