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
What’s a Package?
Comparison of 2GP and 1GP Managed Packages
Namespaces
Package IDs and Aliases
Before You Create Second-Generation Managed Packages
Know Your Orgs
Workflow for Second-Generation Packages
Configure Packages
Best Practices for Second-Generation Managed Packages
Frequently Used Packaging Operations
Create a Package
Push a Package Upgrade
Install a Package
Uninstall a Package
Publishing Your App on AppExchange
Gaps Between First-Generation and Second-Generation Managed Packaging
Test and Respond to the New Order Save Behavior
Unlocked Packages
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Newer Version Available

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

Know Your Orgs

Some of the orgs that you use with second-generation managed packaging have a unique purpose.

Choose Your Dev Hub Org

Use the Dev Hub org for these purposes.
  • As owner of all second-generation managed packages
  • To link your namespaces
  • To authorize and run your force:package commands

We recommend that your Partner Business Org is also your Dev Hub org.

Note

Namespace Org

The primary purpose of the namespace org is to acquire a package namespace. If you want to use the namespace strictly for testing, choose a disposable namespace.

After you create a namespace org and specify the namespace in it, open the Dev Hub org and link the namespace org to the Dev Hub org.

Other Orgs

When you work with packages, you also use these orgs:
  • You can create scratch orgs on the fly to use while testing your packages.
  • The target or installation org is where you install the package.