When I have Batarang chrome extension enabled, if I try to load this polyfill into any angular 1.3 or 1.4 versions, ng fails to bootstrap and throws the error below.
Problem goes away and .component works great as soon as I disable the batarang extension (... found I later day one...)
angular.js:4087
Uncaught Error: [$injector:modulerr] http://errors.angularjs.org/1.3.0/$injector/modulerr?p0=app&p1=TypeError%3A…nsion%3A%2F%2Fighdmehidhipcmcojjgiloacoafjmpfk%2Fdist%2Fhint.js%3A569%3A11)
at https://code.angularjs.org/1.3.0/angular.min.js:6:416
at https://code.angularjs.org/1.3.0/angular.min.js:35:459
at r (https://code.angularjs.org/1.3.0/angular.min.js:7:302)
at g (https://code.angularjs.org/1.3.0/angular.min.js:35:33)
at Jb (https://code.angularjs.org/1.3.0/angular.min.js:38:269)
at d (https://code.angularjs.org/1.3.0/angular.min.js:18:3)
at Object.ta.resumeBootstrap (https://code.angularjs.org/1.3.0/angular.min.js:18:407)
at maybeBootstrap (chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:569:11)
I know batarang extension was and is buggy, but it never broke my app like this before, and it's a useful tool in my belt at times..
Any idea why Batarang would break this polyfill?
When I have Batarang chrome extension enabled, if I try to load this polyfill into any angular 1.3 or 1.4 versions, ng fails to bootstrap and throws the error below. Problem goes away and .component works great as soon as I disable the batarang extension (... found I later day one...)
I know batarang extension was and is buggy, but it never broke my app like this before, and it's a useful tool in my belt at times..
sample code I'm using: