Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Enable Dev Hub Features in Your Org
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Track Changes Between Your Project and Org
Development
Build and Release Your App
First-Generation Managed Packages
Second-Generation Managed Packages
Unlocked Packages
What’s a Package
Package-Based Development Model
Before You Create Unlocked Packages
Know Your Orgs
Create Org-Dependent Unlocked Packages
Workflow for Unlocked Packages
Configure Packages
Project Configuration File for Packages
Keywords
Package Installation Key
Extract Dependency Information from Unlocked Packages
Understanding Namespaces
Share Release Notes and Post-Install Instructions
Specify Unpackaged Metadata or Apex Access for Apex Tests
Best Practices for Unlocked Packages
Package IDs and Aliases
Frequently Used Packaging Operations
Create a Package
Push a Package Upgrade
Install a Package
Migrate Deprecated Metadata from Unlocked Packages
Uninstall a Package
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Frequently Used Packaging Operations

For a complete list of Salesforce CLI packaging commands, see: Salesforce Command Line Reference Guide.

Salesforce CLI command What it Does
force:package:create Creates a package. When you create a package, you specify its package type and name, among other things.
force:package:version:create Creates a package version.
force:package:install Installs a package version in a scratch, sandbox, or production org.
force:package:uninstall Removes a package that has been installed in an org. This process deletes the metadata and data associated with the package.
force:package:version:promote Changes the state of the package version from beta to the managed-released state.
force:org:create Creates a scratch org.
force:org:open Opens an org in the browser.