First-Generation Managed Packaging Developer Guide

First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Move to 2GP: Migrate Your Managed Packages with Ease
Register a Namespace for a First-Generation Managed Package
Create a First-Generation Managed Package Using a UI
Create a First-Generation Managed Package using Salesforce DX
Enable Dev Hub and Second-Generation Managed Packaging
Limited Access License for Package Developers
Add a Limited Access User to Your Dev Hub Org
Link a Namespace to a Dev Hub Org
Scratch Orgs and Package Development
Build and Release Your App with Managed Packages
Packaging Checklist
Deploy the Package Metadata to the Packaging Org
Create a Beta Version of Your App
Install the Package in a Target Org
Create a Managed Package Version of Your App
View Information About a Package
Components Available in First-Generation Managed Packages
Behavior of Specific Metadata in First-Generation Managed Packages
Package and Test Your First-Generation Managed Package
Update Your First-Generation Managed Package
Publish Upgrades to First-Generation Managed Packages
Manage Licenses for Managed Packages
Manage Features in First-Generation Managed Packages
AppExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Packaging Checklist

Ready to deploy your packaging metadata and start creating a package? Take a few minutes to verify that you covered the items in this checklist, and you’re good to go.
  1. Link the namespace of each package you want to work with to the Dev Hub org.
  2. Copy the metadata of the package from your version control system to a local project.
  3. Update the config files, if needed.
    For example, to work with managed packages, sfdx-project.json must include the namespace.
    1"namespace": "acme_example",
  4. (Optional) Create an alias for each org you want to work with.

    If you haven’t yet created an alias for each org, consider doing that now. Using aliases is an easy way to switch between orgs when you’re working in the CLI.

  5. Authenticate the Dev Hub org.
  6. Create a scratch org.
    A scratch org is different than a sandbox org. You specify the org shape using project-scratch.json. To create a scratch org and set it as the defaultusername org, run this command from the project directory. 
    1sf org create scratch --definition-file config/project-scratch-def.json
  7. Push source to the scratch org.
  8. Update source in the scratch org as needed.
  9. Pull the source from the scratch org if you used declarative tools to make changes there.

With these steps complete, you’re ready to deploy your package metadata to the packaging org.