Lightning Aura Components Developer Guide

Introducing Aura Components
Quick Start
Creating Components
Component Names
Create Aura Components in the Developer Console
Create Aura Components Using Salesforce CLI
Component Markup
Component Namespace
Using the Default Namespace in Organizations with No Namespace Set
Using Your Organization’s Namespace
Using a Namespace in or from a Managed Package
Creating a Namespace in Your Organization
Namespace Usage Examples and Reference
Component Bundles
Component IDs
HTML in Components
CSS in Components
Component Attributes
Using Expressions
Component Composition
Component Body
Component Facets
Controlling Access
Using Object-Oriented Development
Best Practices for Conditional Markup
Aura Component Versioning for Managed Packages
Base Components with Minimum API Version Requirements
Validations for Aura Component Code
Using Labels
Localization
Working with Lightning Base Components
Supporting Accessibility
Writing Documentation for the Component Library
Using Components
Communicating with Events
Communicating Across the DOM with Lightning Message Service
Creating Apps
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.

Creating a Namespace in Your Organization

Create a namespace for your organization by registering a namespace prefix.

If you’re not creating managed packages for distribution then registering a namespace prefix isn’t required, but it’s a best practice for all but the smallest organizations.

Your namespace must:
  • Begin with a letter
  • Contain one to 15 alphanumeric characters
  • Not contain two consecutive underscores

For example, myNp123 and my_np are valid namespaces, but 123Company and my__np aren’t.

To register a namespace in an org, use a Developer Edition org that’s separate from your Dev Hub or scratch orgs.

Note

To register a namespace:
  1. From Setup, enter Package Manager in the Quick Find box and select Package Manager.
  2. In the Namespace Settings panel, click Edit.

    After you’ve configured your namespace settings, this button is hidden.

    Note

  3. Enter the namespace you want to register.
  4. Click Check Availability to determine if the namespace is already in use.
  5. If the namespace prefix that you entered isn’t available, repeat the previous two steps.
  6. Click Review.
  7. Click Save.

Next, you can link the namespace to a Dev Hub org, which you can use to manage scratch orgs and build second-generation packages (2GP) for distribution.