Find Component Markup Errors Faster with Improved Error Messages

We display more details for more Lightning component errors. It’s now easier for your users to report errors they encounter, and for you to find and fix those errors. This change affects all users, and doesn’t depend on debug mode being enabled.

Does this feature sound familiar? That’s because we’re expanding the improved error messages we introduced in Spring ’17. In that release, we improved the details and presentation of some kinds of errors—specifically, server-side errors caused by incorrect component markup. This release expands the range to include client-side JavaScript run-time errors. These kinds of errors are far more common, and the lack of meaningful details sometimes made debugging harder.

Expanded Error Panel (Summer ’17) Error Panel With Limited Details (prior releases)
Lightning components expanded error reporting panel Lightning components old error reporting panel


The new error panel doesn’t have an OK button. To dismiss the panel, click the “X” in the top right.

The error panel appears only when a relevant error occurs in Lightning Experience or Salesforce1. The expandable stack trace appears only on desktop and tablet form factors—not on a phone.

The improved error reporting affects only your custom components, not standard components provided with the framework. Outside of Lightning Experience and Salesforce1, for example, in Lightning Out or a standalone app, error output can include details that were previously omitted, such as a complete stack trace.