LWCIntermediateeslintcicdquality
Architect LWC CI/CD with ESLint and Prettier standards
Real World Scenario
Inconsistent LWC code styles and @lwc/lwc/no-async-operation violations reach production.
Expected Answer
• @lwc/eslint-plugin rules in CI blocking merge
• Prettier formatting enforced pre-commit
• Jest run in pipeline on every PR
• Sfdx scanner security rules for LWC Apex pairs
• Component catalog generated from repo metadata
• Version pinning eslint jest sfdx-lwc-jest
• Document team conventions in CONTRIBUTING.md
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: @lwc/eslint-plugin rules in CI blocking merge Also consider: Prettier formatting enforced pre-commit In practice: Jest run in pipeline on every PR Balance speed of delivery with maintainability.
Architect Perspective
Lint in CI is cheapest quality gate—architects enforce before code review human time.