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
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
Validation When You Save Code Changes
Validation During Development Using ESLint
Aura Component Validation Rules
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

Validation During Development Using ESLint

Use ESLint to scan and improve your code during development. A linting tool doesn’t just help you avoid Lightning Locker conflicts and anti-patterns. It’s a terrific practice for improving your code quality and consistency, and to uncover subtle bugs before you commit them to your codebase.

Validations using ESLint are done separately from saving your code to Salesforce. The results are informational only.

Salesforce DX used to include a force:lightning:lint command but the command was removed in February, 2022. Instead, we recommend the Aura plugin for ESLint for linting.

To install the Aura plugin for ESLint, see this GitHub repo.

Validations performed using the Aura plugin for ESLint are different from validations performed at save time in the following important ways.
  • ESLint uses many more rules to analyze your component code. Save-time validations prevent you from making the most fundamental mistakes only. Validation with ESLint errs on the side of giving you more information.
  • Validation via ESLint ignores the API version of your components. Save-time validations are performed only for components set to API 41.0 and later.