The Apex and Deploy/Retrieve commands are in the process of moving to a new architecture. We moved these commands to independent Typescript libraries and CLI plugins as part of our larger effort to break up the salesforce-alm plugin. You can read more about that in this blog post. There’s many great benefits to this effort and one of the best is better performance. For single file deploys and retrieves, you’ll likely notice a significant performance gain when using the latest architecture.
Execution Process and Status
This architecture change is done through a phased approach. For both the Apex library and Deploy/Retrieve library, we are rolling out the changes through these phases:
- Library created and completed.
- Available to try it in VS Code - We provide a VS Code setting so you can opt in and try it out.
- On by default in VS Code - The VS code setting default is defaulted to True to enable the library. If you previously opted in and then opted out, you’ll have to manually opt back in to use the feature. We’ll change the default after the commands have been available and used for months.
- CLI updated to use the library. The VS Code setting is then retired. Both the CLI and VS Code extensions are using the library.
|Library complete||Available to try in VS Code||On by default in VS Code||CLI Updated|
|Deploy Retrieve Library||✔️||✔️||✔️|
The Apex library has been fully implemented, but the Deploy/Retrieve library has a corresponding VS Code setting. Access the Deploy/Retrieve setting by selecting Select File > Preferences > Settings (Windows or Linux) or Code > Preferences > Settings (macOS). Setting to false means that VS Code uses the CLI to execute these commands.
Within settings, you will see the following:
- Experimental: Deploy Retrieve
- If you’re using CLI Plug-In Hooks, they are not available when using the library from VS Code. Uncheck the settings above to use the CLI directly for those commands.
If you spot other gaps or have feedback, please open a GitHub issue.