Lightning Components Developer Guide
Summer '26 (API version 67.0)
Spring '26 (API version 66.0)
Winter '26 (API version 65.0)
Summer '25 (API version 64.0)
Spring '25 (API version 63.0)
Winter '25 (API version 62.0)
Summer '24 (API version 61.0)
Spring '24 (API version 60.0)
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Spring '20 (API version 48.0)
Winter '20 (API version 47.0)
Summer '19 (API version 46.0)
Spring '19 (API version 45.0)
Winter '19 (API version 44.0)
Summer '18 (API version 43.0)
Spring '18 (API version 42.0)
Winter '18 (API version 41.0)
Summer '17 (API version 40.0)
Spring '17 (API version 39.0)
Winter '17 (API version 38.0)
Summer '16 (API version 37.0)
Spring '16 (API version 36.0)
Winter '16 (API version 35.0)
Summer '15 (API version 34.0)
Spring '15 (API version 33.0)
Winter '15 (API version 32.0)
App Overview
Designing App UI
Creating App Templates
Validation When You Save Code Changes
Review and Resolve Validation Errors and Warnings
Salesforce Lightning CLI (Deprecated)
Using the AppCache
Distributing Applications and Components
Newer Version Available
Validations for Lightning Component Code
Validate your Lightning component code to ensure compatibility with Lightning component
APIs, best practices, and avoidance of anti-patterns. There are several ways to validate your
code. Minimal save-time validations catch the most
significant issues only, while Salesforce DX tools provide more comprehensive static code
analysis.
-
Validation When You Save Code Changes
Lightning component JavaScript code is validated when you save it. Validation ensures that your components are written using best practices and avoid common pitfalls that can make them incompatible with LockerService. Validation happens automatically when you save Lightning component resources in the Developer Console, in your favorite IDE, and via API. -
Validation During Development Using the Salesforce CLI
Salesforce DX includes a code analysis and validation tool usable via the Salesforce CLI. Use force:lightning:lint to scan and improve your code during development. Validation using the Salesforce CLI doesn’t just help you avoid LockerService 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. -
Review and Resolve Validation Errors and Warnings
When you run validations on your Lightning component code, the results include details for each issue found in the files scanned. Review the results and resolve problems in your code. -
Lightning Component Validation Rules
Rules built into Lightning component code validations cover restrictions under LockerService, correct use of Lightning APIs, and a number of best practices for writing Lightning component code. Each rule, when triggered by your code, points to an area where your code might have an issue. -
Salesforce Lightning CLI (Deprecated)
Lightning CLI was a Heroku Toolbelt plugin to scan your code for general JavaScript coding issues and Lightning-specific issues. Lightning CLI is deprecated in favor of the force:lightning:lint tool available in the Salesforce DX CLI.