Definition
Lightning Components is a Setup page that lists all Lightning components (both Aura and Lightning Web Components) available in the org, including those from installed packages. It provides developers with an inventory of reusable UI components that can be placed on Lightning pages, Experience Cloud sites, and flows.
Real-World Example
A developer at CloudBridge Solutions opens the Lightning Components page in Setup to browse all available components. She finds a custom Aura component called "AccountMap" built by a previous developer and a Lightning Web Component called "dealScorecard" from an installed package. She uses both on a new Lightning record page without writing any new code.
Why Lightning Components Matters
Lightning Components is the Setup page in Salesforce that provides a complete inventory of all Lightning components available in the org, including both Aura components and Lightning Web Components (LWC), as well as those installed from managed packages. This inventory solves the problem of component discoverability—developers and admins can browse what is already available before building something new, preventing duplicate development effort. Each listed component shows its type, namespace, and description, making it easy to assess whether an existing component meets a requirement or needs to be extended.
As organizations accumulate custom components from internal development and installed packages, the Lightning Components page becomes essential for governance and reuse. Without a centralized inventory, teams often build redundant components because they are unaware of existing ones, leading to maintenance overhead and inconsistent user experiences. The page also helps administrators understand which components are available for placement in Lightning App Builder, Experience Cloud sites, and Flows. Organizations that neglect component governance often end up with dozens of similar components that behave slightly differently, confusing users and creating technical debt that becomes expensive to rationalize during platform upgrades.
How Organizations Use Lightning Components
- CloudBridge Solutions — A developer at CloudBridge Solutions opened the Lightning Components page and discovered an existing Aura component called 'AccountMap' built by a previous developer and a Lightning Web Component called 'dealScorecard' from an installed package. She used both on a new record page without writing any code, saving two weeks of development time.
- TechForward Inc — TechForward Inc's architecture team used the Lightning Components inventory to conduct a quarterly audit, discovering 15 custom Aura components that duplicated functionality already available in newer LWCs. They consolidated down to 8 components, reducing their maintenance burden by 40% and improving page load times across the org.
- Prism Retail — Prism Retail's admin browsed the Lightning Components page to find all components available from their three installed AppExchange packages. She assembled a custom Store Manager page using components from different packages—a foot traffic heatmap, an inventory alert panel, and a sales leaderboard—creating a unified dashboard without any custom development.