-
Notifications
You must be signed in to change notification settings - Fork 27.4k
ngAnimate after update to 1.5 i keep getting tons of TypeError messages. #13395
Comments
It would be good if you could isolate the error and show it in a demo, otherwise we cannot do anything.
|
Same here. Updated from 1.4.8 to 1.5.0-build.X Lots of ng-show directives.
|
Is it possible you have some old version of the angular.js file cached? |
I am using a lot of ng-show and I have updated libs from 1.4.8. Below libs I use from bower.json:
From the debbuger, object does not have done() function
|
Can someone of you please post a demo to plnkr.co or similar? |
Experiencing same issue with 1.5 |
@blazingAvatar The (beta) versions of angular and angular-animate must match: http://plnkr.co/edit/EGkylQ?p=preview |
I have wrongly assumed that this will resolve to the same version. Thank you for your help. |
Thanks for the help. |
Looks like this is resolved then! |
I got this error when my version of angular was 1.4.7 and version of angular-animate being 1.5.4. Switching the version of angular-animate to 1.4.7 did the trick |
Even angular 1.4.4 and angular-animate 1.4.10 will cause this be careful to lock your dependencies. I had
and got 1.4.10 installed lock it down:
|
@crucialfelix, note that you should always have matching version of core angular and external angular modules (e.g. angular-animate). Non-matching versions are not guaranteed to work together. |
Yes thanks, I know that. But because I had used |
I'm using it with meteor and getting same error. Here are my versions
|
Oopps.. i'm new on meteor so package.json is not same version that were inside meteor (i couldnt get anyway). meteor update angular:angular And it upgraded from 1.4.8 to 1.5.3_1 Thanks to: |
^ solved my problem too. Needed to update my 1.4.8 to 1.5 |
same problem is resolved by using |
I have updated my project to Angular 1.5 and I started getting this errors on the console.
#1.5.0-build.4406+sha.7ffb2d3
angular-animate#1.5.0-build.4406+sha.7ffb2d3
The text was updated successfully, but these errors were encountered: