Is there a better way to understand angular error / exception messages in AngularJS?
During development, we often encounter errors / exceptions in the developer console. But for me its not easy to correctly recognize the error (: P). Is there a better way to get more information about the error / exception, for example due to which code, line number, which line, etc.
Thank!
+3
Hrishikesh
source
to share
1 answer
Use Chrome for debugging. In Chrome, Angular messages appear as a nice stracktrace with a clickable link to the error description.
You can also use an invalid Angular version to get more detailed error messages.
+3
wvdz
source
to share