Delete Lightning Components from Managed Packages

You can delete an Aura or Lightning web component from a managed package after it’s released. This change enables you to refactor a package and delete any components that are no longer needed.

Where: This change applies to Aura and Lightning web components in managed packages in Lightning Experience and Salesforce Classic.

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

To delete an Aura or Lightning web component:

  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 or Lightning web 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 a Lightning web component or an Aura component with a public or global access value.

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. Allow a Lightning web component to be used in Lightning App Builder or Experience Builder by setting isExposed to true in the component’s configuration file.

We recommend a two-stage process to package developers when you delete an Aura component with global access or a Lightning web component with an isExposed value of true. 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.