Reviews of Angular state inspector

By: Ihor Klymenok Add-on

List of user reviews and ratings for Angular state inspector

Total ratings

3.42 (Rating count: 12)

Receive review notifications

Get notified when new reviews are posted so you can respond quickly.

See reviews on Firefox Add-ons Store

View and respond to reviews directly on the store page.

Visit

Review summary

Angular state inspector for Firefox enables state inspection for Angular projects and serves as a crucial debugging tool after Augury's failure in Firefox. Users appreciate its functionality and utility, especially for transitioning from Chrome. However, it suffers from usability issues, including poor documentation, interface instability with custom components, and inconvenient tab placement in the inspector. Additionally, some users report that it does not run properly in Firefox at times.

Pros

Allows inspection of Angular state within Firefox's Inspector tool for locally running Angular projects.
Provides a necessary alternative for Angular debugging in Firefox, especially after the Augury tool broke.
Useful enough to assist users in switching from Chrome to Firefox due to its functionality.

Cons

The extension is not very user-friendly or intuitive; users find it difficult to understand how to use it due to lack of documentation or guides.
Sometimes the application's interface breaks, especially for custom Angular components.
The 'State' tab is located inconveniently at the end of the inspector panel, making it cumbersome to access, partly due to Firefox limitations.
In some cases, the add-on does not run or work properly in Firefox, as reported by multiple users.

Upgrade to see all 16 reviews

User Reviews

Recent rating average: 4.30

All time rating average: 3.42

Upgrade to see all 16 reviews

13% (2)

Date	Author	Comment
2025-04-06	敬念*****

2025-02-10	远离*****

2022-12-27	翻墙*****	欢迎光临翻墙部落! 打开天窗，听听外面的声音! 穿越迷雾，寻找人生真谛! https://github.com/osurf/jzdy/blob/master/README.md?
欢迎光临翻墙部落! 打开天窗，听听外面的声音! 穿越迷雾，寻找人生真谛! https://github.com/osurf/jzdy/blob/master/README.md?
2022-12-22	Ga*****	Gan Jing World is a clean, curated universe and a dynamic, overlapping network of integrated platforms and services. ==> https://www.ganjing.com
Gan Jing World is a clean, curated universe and a dynamic, overlapping network of integrated platforms and services. ==> https://www.ganjing.com
2022-02-02	No*****	Does what it says. You can inspect the state in the Inspector tool on a locally running Angular project. It is not as convenient as other dev tools such as for Vue or React.
Does what it says. You can inspect the state in the Inspector tool on a locally running Angular project. It is not as convenient as other dev tools such as for Vue or React.
2021-06-01	wj*****	it app no run in firefox
it app no run in firefox
2020-12-13	Is*****	First of all, I'm very thankful this exists. Now that augury in firefox is broken, this is my only way to effectively debug in angular on that browser. it is functional and I like it. However, it does seem like sometimes the application's interface sort of breaks. At least it does for my custom components.
First of all, I'm very thankful this exists. Now that augury in firefox is broken, this is my only way to effectively debug in angular on that browser. it is functional and I like it. However, it does seem like sometimes the application's interface sort of breaks. At least it does for my custom components.
2020-10-26	Ca*****

2020-06-09	Va*****	Kinda difficult to use because the "State" tab is located at the very end of the inspector panel, which means it definitely takes a lot more space than it needs, not necessarily your fault, firefox is the one to blame here. But I guess you could create a new major tab (along with "inspector", "debugger", "network", etc.) which contains the whole virtual dom tree, this way you can skip the native HTML elements which don't have angular state too! (although you can consider to add those as properties shown like `template` or `child` etc)
Kinda difficult to use because the "State" tab is located at the very end of the inspector panel, which means it definitely takes a lot more space than it needs, not necessarily your fault, firefox is the one to blame here. But I guess you could create a new major tab (along with "inspector", "debugger", "network", etc.) which contains the whole virtual dom tree, this way you can skip the native HTML elements which don't have angular state too! (although you can consider to add those as properties shown like `template` or `child` etc)
2020-04-03	Ев*****	Отличное расширение, которое позволило окончательно перейти с хрома на firefox. Разработчику успехов!
Отличное расширение, которое позволило окончательно перейти с хрома на firefox. Разработчику успехов!