Description from extension meta
For inspecting Lightning apps
Image from store
Description from store
The Salesforce Lightning Inspector opens up and improves your Lightning Component development, giving you access to a wealth of data about your running applications and components.
With the Salesforce Lightning Inspector you can:
- Easily inspect and navigate the structure of your components
- Identify performance bottlenecks by looking at a graph of component creation time
- Debug server interactions faster by monitoring and modifying responses
- Navigate the component tree, inspect components and their associated DOM elements
- Track event firing and handling sequences
Update July 10, 2020
Changed to only allow use with Salesforce URLs to comply with Google policy. The inspector will not work with Lightning Out hosted on non-Salesforce URLs.
Update March 19, 2019
Added Lightning Stylesheet Previewer
Update Sept 7, 2018
Bug Fixes
Update Dec 27, 2016
Version 1.0.1.2
Improvements and new features:
Actions Tab shows the component that fired the action.
Chaos Manager improvements
Lightning Inspector leverages SLDS
Transactions Grid:
- Include custom transactions
- Better timing measurements (now show ms since page load)
- Disabled the server performance timings for actions (clicking on an action will do nothing for now)
- Fixed timeline sizing and colors.
- Tooltip to the graph bars to show start and end times.
Lightning Out support
LI now works on every page that has Aura.
Only instruments the page when you launch Lightning Inspector
Bug fixes
Update October 4, 2016
Get component descriptions from more product areas, see transactions graphically, review event call stacks, and get the Salesforce Lightning Inspector DevTools extension in more languages.
Update June 30, 2015
v1.0.0.6
Bug fix.
v1.0.0.5: More bug fixes
Update June 8, 2016
v1.0.0.4: This is mostly a bug fix release, but a few helpful features have been added.
* Event handlers should show up
* Component view has less redundant information
* Double click on components in more places to navigate around the component tree
* Additional value providers show up in the component view (helpful for iteration and if)
Update Oct 11, 2017
* Fixes a bug when serializing the component tree
* New Faster component tree
* Implemented search (Ctrl+F) for Component tree
Latest reviews
- (2020-02-06) Kostadin Stoev: Doesn't work as of Chrome 80
- (2019-12-17) Prasad Kothawade: Not even 1 star not working at all..
- (2019-11-04) Deepak Anand: As other reviews mentioned, getting error "From an Embedded Page at pcpmcffcomlcjgpcheokdfcjipanjdpc , Error getting marks inspected window" etc... And there is no one looking to fix these.
- (2019-10-29) Bartosz Śliwiński: The tool is great but I cannot use 'Performance' tab because of 'Error clearing marks on inspected window'
- (2019-10-03) RAC Website: It doesn't always appear to work in inspecting crucial lightning objects when selected in the Developer Console. Which is a shame as it enabled me to quickly identify what the field selected was in relation to. It has helped though massively in troubleshooting and diagnosing problems with Apex and lightning callbacks from components.
- (2019-10-01) Erin Agobert: I haven't been able to use this extension yet. I was pretty excited to use, but when I go to inspect a lightning component, the inspector is blank. The developer resources for finding assistance lead to a general help site. I can't recommend this extension to anyone.
- (2018-10-17) Antero Karttunen: Component tree expands and then hides everything, can't do anything with this extension.
- (2018-10-04) Sergey Yakutin: This is really bad extension that always crashed.
- (2018-09-17) Mike Topalovich: Not understanding the poor reviews - this tool is a lifesaver. There are occasional quirks with scrolling, and there are issues that surface with new releases of Salesforce and/or Chrome, but for all intents and purposes this is the de facto tool for troubleshooting Lightning Components. The ability to monitor Actions and Events alone makes this plugin worth its weight in gold.
- (2018-08-02) Jason Clark: Just doesn't work.
- (2018-04-02) Chenda Chhean: It is not working for most of functionalities. example of 1 of errors in performance tab "From an Embedded Page at pcpmcffcomlcjgpcheokdfcjipanjdpc , Error getting marks inspected window" etc...
- (2018-03-27) Валентин Біленький: Terrible, search does not work, hangs up often
- (2018-02-12) Kenneth Sørensen: This is bad, really BAD!!! Searching is not even working inside elements.... Salesforce is really needing to do something with this and the tooling for the developers...
- (2017-09-26) Luke Kozakewycz: Horizontal scrolling doesn't work and panels are not adjustable so content is mostly hidden. Idea is good - it just needs work.
- (2017-09-13) Michael Covert: Only works if I use it with Developer Console, never works when I try to open the Lightning tab anywhere else with Lightning components it will just continue to load forever.
- (2017-07-14) soniacookbroen: I was able to uninstall and reinstall and it works but do not click component tree or you will get the loading dots for... ever!!!
- (2017-07-10) I have installed it several times on various machines, it never works.
- (2017-06-30) Evgen Kasyan: Override actions doesnt work!
- (2017-05-15) Chaitanya Kumar V: Not able to view performance Tab results. Always get below error Error getting marks inspected window
- (2017-02-13) Vitaly Zdanevich: please provide optional dark theme
- (2016-12-20) Sushil Kumar: It doesn't work at my chrome, Lightning tab appears, but nothing displayed after on clicking on this. I don't what is the missing or issue. Please help me for the same.
- (2016-10-02) Andy Rouse: I've used this on some computers and it has worked fine. But on other computers the Lightning tab never shows up in the developer tools. This inconsistency needs to be resolved.
- (2016-08-10) Nicolas Vuillamy: Hi, Good extensions, but I have an issue with the display on components with inheritance. Example: CmpRoot is an abstract component containing a ltng:require + {!v.body}. CmpChild extends CmpRoot and use other sub components like CmpMyOtherComponent In the components tree, CmpChild is displayed, but i just see the ltng:require, but not the body of the component, so all sub components of CmpChild are not visible
- (2016-07-18) Dmitry Omelchenko: Great tool! Although the searching functionality doesn't work in the Component Tree tab. Hope it will be fixed soon. I'm on OS X 10.11.5, Chrome version: 51.0.2704.106.
- (2016-04-13) Gopal Rao: Great tool, saves you from writing console logs everywhere and helps you debug your app in less time. It would have been really great if in-line editing is allowed in the mark-up (not sure if it is feasible to add this feature)