I am sure no one told you these Angular debug tips (Part 2)😱

Hope you like part 1 angular APIs, but you get excite to know more APIs which we will explore in this article.

If you didn’t check Part 1, here you go https://ankitsrivastavablog.medium.com/i-am-sure-no-one-told-you-these-angular-debug-tips-part-1-be29daa124f7


The ng.getDirectives() function returns an array of Angular directives that are applied to an element in the DOM.

Using this, we can not only determine what directives are being applied to the element, but we can also access a specific directive instance

Here is a screenshot showing the result of the getDirectives() function.


The ng.getListeners() function returns an array of DebugEventListener objects. Using the DebugEventListener object you can examine the name of the event that triggers each listener.

I didn’t found any example for this method, if I do, I’ll post in comment.


The ng.getHostElement() function accepts a directive (remember a component is a directive with a template) and returns the native host element.

Let’s look at an example:


Retrieves all root components associated with a DOM element, directive, or component instance. Root components are those which have been bootstrapped by Angular.

These are available APIs by angular official doc Angular — @angular/core/global. You can try and explore more on this, but these APIs use properly, I am sure you can debug the whole angular application in console itself with it property and component assessable.

Happy coding and enjoy bug list.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store