Lightning Components Developer Guide

What is the Lightning Component Framework?
Quick Start
Creating Components
Using Components
Communicating with Events
Creating Apps
App Overview
Designing App UI
Creating App Templates
Developing Secure Code
Validations for Lightning Component Code
Validation When You Save Code Changes
Validation During Development Using the Salesforce CLI
Use force:lightning:lint
force:lightning:lint Options
Custom “House Style” Rules
Review and Resolve Validation Errors and Warnings
Lightning Component Validation Rules
Salesforce Lightning CLI (Deprecated)
Styling Apps
Using JavaScript
JavaScript Cookbook
Using Apex
Lightning Data Service
Lightning Container
Controlling Access
Using Object-Oriented Development
Using the AppCache
Distributing Applications and Components
Debugging
Fixing Performance Warnings
Reference
PDF

Newer Version Available

This content describes an older version of this product. View Latest

force:lightning:lint Options

Use options to modify the behavior of force:lightning:lint.

Common Options

Filtering Files

Sometimes, you just want to scan a particular kind of file. The --files argument allows you to set a pattern to match files against.

For example, the following command allows you to scan controllers only:

1sfdx force:lightning:lint ./path/to/lightning/components/ --files **/*Controller.js

Verbose Mode

The default output shows only errors so you can focus on bigger issues. The --verbose argument allows you to see both warning messages and errors during the linting process.

For a complete list of command line parameters and how they affect tool behavior, see the Salesforce CLI Command Reference.

force:lightning:lint has built-in help, which you can access with the following command:
1sfdx force:lightning:lint --help