Upon using angular.js, I encountered the following stack trace:
[$injector:unpr] Unknown provider: editorPopupManagerProvider <- editorPopupManager <- libStateManager <- libInjectionManager
http://errors.angularjs.org/1.2.2/$injector/unpr?p0=editorPopupManagerProvider%20%3C-%20editorPopupManager%20%3C-%20libStateManager%20%3C-%20libInjectionManager
And when utilizing angular.min.js, this was the resulting stack trace:
[$injector:unpr] http://errors.angularjs.org/1.2.2/$injector/unpr?p0=editorPopupManagerProvider%20%3C-%20editorPopupManager%20%3C-%20libStateManager%20%3C-%20libInjectionManager
Although a simple example, at times the minified error provides little assistance.
In both scenarios - with angular.js and angular.min.js, I anticipate encountering the initial stack trace. The deliberate introduction of this issue in my code highlights the challenge posed by angular.min.js's obscured stack trace, making comprehension difficult. While I appreciate the intent behind obscuring stack traces from end users, for logging purposes, I require clear, readable stack traces to be sent to a logging server.