When developing my client's website, I utilized Angular JS 1.5.7. A unique dynamic mechanism was put in place to seamlessly integrate remote JS applications on the site. This process begins by loading a configuration file that specifies which additional scripts and stylesheets need to be loaded. However, one of the applications being loaded is using Angular JS version 1.3.9, causing an error due to version incompatibility with the ngAnimate module.
Initially, my solution involved moving window.angular
to window.vendor.angular
and deleting window.angular
to ensure compatibility with the remote Angular JS version. Unfortunately, this approach led to complications as Angular JS relies on $window.angular at multiple points throughout the codebase.
In search of a better alternative, simply replacing window.angular
and $window.angular
is not feasible since I prefer to load AngularJS from a public CDN for performance reasons.
Currently, I am exploring ways to run Angular JS in complete isolation or implement something similar to jQuery.noConflict()
from the jQuery library to resolve this issue seamlessly.