Lightning Aura Components Developer Guide

Introducing Aura Components
Quick Start
Creating Components
Using Components
Communicating with Events
Communicating Across the DOM with Lightning Message Service
Creating Apps
App Overview
Designing App UI
Creating App Templates
Using the AppCache
Distributing Applications and Components
Apex Class Considerations for Packages
Adding Aura Components to Managed Packages
Deleting Aura Components from Managed Packages
Styling Apps
Developing Secure Code
Using JavaScript
Working with Salesforce Data
Testing Components
Debugging
Performance
Reference
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Deleting Aura Components from Managed Packages

After you’ve released a managed package, you may decide to refactor the package and delete an Aura component. It’s your responsibility to educate your customers about the potential impact from any components you delete. In the Release Notes for your upgraded package, list all custom components you’ve deleted and notify customers of any necessary actions.

To enable component deletion in your packaging org, log a case in the Partner Community.

Note

To delete an Aura component from a managed package:

  1. From Setup, enter Lightning Components in the Quick Find box.
  2. Select Lightning Components.
  3. Click Del for the component that you want to delete.Lightning Components in Setup

You can delete an Aura component from the Developer Console also.

When a developer removes an Aura component from a package, the component remains in a subscriber’s org after they install the upgraded package. The administrator of the subscriber’s org can delete the component, if desired. This behavior is the same for an Aura component with a public or global access value.

Note

The access attribute on the aura:component tag can be set to public or global to control whether the component can be used outside of the component’s namespace.

We recommend a two-stage process to package developers when you delete an Aura component with global access. This process ensures that a global component that you delete from the package has no dependencies on the other items in the package.

  1. Stage one: Remove references
    1. Edit the global component that you want to delete to remove all references to other Lightning components.
    2. Upload your new package version.
    3. Push the stage-one upgrade to your subscribers.
  2. Stage two: Delete your obsolete component
    1. Delete the global Lightning component from the package.
    2. Optionally, delete other related components and classes.
    3. Upload your new package version.
    4. Push the stage-two upgrade to your subscribers.