Salesforce DX Developer Guide

Release Notes
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
Create a First-Generation Managed Package using Salesforce DX
Second-Generation Managed Packages
Partner Licensing Platform (Developer Preview)
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
How We Handle Profile Settings in Unlocked Packages
Create a Package
Push a Package Upgrade
Install a Package
Migrate Deprecated Metadata from Unlocked Packages
Uninstall a Package
Transfer an Unlocked Package to a Different Dev Hub
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Newer Version Available

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

Unlocked Packages

Salesforce offers different types of packages, and unlocked packages are especially suited for internal business apps. Unless you plan to distribute an app on AppExchange, an unlocked package is the right package type for most use cases. You can use unlocked packages to organize your existing metadata, package an app, extend an app that you’ve purchased from AppExchange, or package new metadata.

Unlocked packages follow a source-driven development model. The source of truth of the metadata contained in the package is your version control system, not what’s in an org. This model brings with it all the benefits of modern source-driven development models.

If you’re an AppExchange partner that plans to distribute your app to customers via AppExchange, second-generation managed packaging is the preferred tool. See Second-Generation Managed Packages for more information.

Note