Install the Salesforce Extension Pack extension (and any other extensions that you use for Salesforce development). NOTE: The first time you launch code-sfdx, it has no extensions because it’s a fresh instance VS Code. Add this line to your shell’s startup script.Įither open a new terminal window or run one of the following commands from your current terminal.įrom the terminal, run code-sfdx to launch an instance of VS Code that has only your extensions.bashrc in your home directory (for example, in Macintosh HD/users/yourName). If you don’t have a file with these names, create a file called.
If you’re using Z Shell, it’s typically your. If you’re using Bash, the startup script is typically your. In your favorite terminal, open your shell’s startup script. This command lets you invoke `code` directly from your favorite terminal. Run the command Shell command: Install ‘code’ command in PATH.
To open the Command Palette, press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Linux). If you don’t, create it by running:Īlias code-sfdx='code -extensions-dir ~/.sfdx-code' (Git Bash is installed as part of Salesforce CLI.) See Visual Studio Code on Windows in the Visual Studio Code docs for details. When you install VS Code, install code as part of your prompt. Here’s how to set up VS Code to launch with only the extensions for working with Salesforce.Īdd a code-sfdx alias to your shell’s startup script. Having only the extensions that you need helps minimize the VS Code startup time and ensures that shortcut keys don’t interfere with one another. Organizing your VS Code extensions by development task can help you avoid having extensions provide functionality that’s not useful for the task at hand. NOTE: Because Code Builder is a web-based, these tips are not of relevance if Code Builder is your development environment of choice. Organize Your VS Code Extensions by Development Task
0 kommentar(er)
