An app I work on uses Angular somewhat sparingly. Essentially, it is a collection of mini-apps that do no interact, some of which use Angular and some of which don't.
Because angular-bugsnag calls Bugsnag.noConflict(), this makes the global Bugsnag object unavailable outside of an angular app. I think.
The reason this is a problem is that my app is a Rails app and, via the asset pipeline, all JS is packed together in one file. So, the inclusion of angular-bugsang 'eats up' this reference, meaning that I cannot use Bugsnag outside of angular.
Is there any reason angular-bugsnag is using noConflict()? How would I go about changing that behavior?
An app I work on uses Angular somewhat sparingly. Essentially, it is a collection of mini-apps that do no interact, some of which use Angular and some of which don't.
Because angular-bugsnag calls
Bugsnag.noConflict()
, this makes the globalBugsnag
object unavailable outside of an angular app. I think.The reason this is a problem is that my app is a Rails app and, via the asset pipeline, all JS is packed together in one file. So, the inclusion of angular-bugsang 'eats up' this reference, meaning that I cannot use Bugsnag outside of angular.
Is there any reason angular-bugsnag is using
noConflict()
? How would I go about changing that behavior?