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
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
Workflow for Second-Generation Packages
Configure Packages
Best Practices for Second-Generation Managed Packages
Frequently Used Packaging Operations
Create a Package
Generate the Package
Generate a Package Version
Create a Patch Version
Package Ancestors
View Package Ancestry
Package Upgrades in Second-Generation Managed Packaging
Package Connected Apps in Second-Generation Managed Packaging
Code Coverage for 2GP Managed Packages
Release a Second-Generation Managed Package
Update a Package Version
Delete a Package or Package Version
View Package Details
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

Create a Package

A package is a top-level container that holds important details about the app or package: the package name, description, and associated namespace.

You supply the package details when you create a package using Salesforce CLI, and the package descriptor section of your sfdx-project.json project configuration file is automatically updated.

You can associate multiple second-generation managed packages with a single Dev Hub org. Unlike first-generation managed packages, a second-generation package has no packaging org.