Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Project Setup
Authorization
Scratch Orgs
Development
Build and Release Your App
Develop Packages (Beta)
Salesforce DX Packaging
Types of Packaging Projects
Before You Create Second-Generation Packages
Workflow for Second-Generation Packages
Plan Second-Generation Packages
Configure Packages
Create a Package
Generate the Package
Generate a Package Version
Package Ancestors
Release a Second-Generation Package
Update a Package Version
View Package Details
Install a Package
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

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 in the package descriptor section of your sfdx-project.json project configuration file. You can associate multiple second-generation packages with a single Dev Hub org. Unlike first-generation managed packages, a second-generation package has no packaging org.

Each package can have many versions. Because you can create multiple second-generation packages with a single org, you can use the Salesforce CLI to see a list of all packages associated with your Dev Hub org.

It’s helpful to review the list before you create a package so you can see previous versions and confirm package details like the status or ID.

Authorize your Dev Hub org, and run the force:package2:list command.

1sfdx force:package2:list