Closed xntrik closed 9 years ago
I am not immediately sure what this issue could be. Potentially a dependency that broke something. Let me know if you discover anything else. Thanks!
I get the same error too when i do a grunt serve.. is it because of version conflicts between the dependencies?
I could resolve this error if I use angular 1.3.15 instead of angular 1.4.3.
Best regards, Raghu.
On Wed, Aug 12, 2015 at 10:40 PM, varwiz notifications@github.com wrote:
I get the same error too when i do a grunt --force
— Reply to this email directly or view it on GitHub https://github.com/mozilla/seasponge/issues/75#issuecomment-130375679.
You can replace the angular-animate file with the latest CDN link and do a build again. This works too.
So this is definitely a dependency out of date issue
I will look into it this weekend. If anyone gets around to it before me checkout out package.json and update the dependency(ies?) there and submit a PR!
For reference was this on OSX, Linux?
I just had the same error (on OSX). I looks like this
Is this the workaround
You can replace the angular-animate file with the latest CDN link and do a build again.
btw the updates branch is also affected
forcing it to 1.3.15 worked.
here is my fix https://github.com/mozilla/seasponge/issues/79#issuecomment-142845405
Thanks for letting us know what worked for you, @DinisCruz.
I have merged #79 could @xntrik @DinisCruz @varwiz @kraghuveer test and reopen if the issue persists?
Have spun up a fresh clone of seasponge. After installing dependencies and spinning up a local server (grunt serve). As soon as I hit the URL (automatically opened in Chrome) I get a blank screen. The console error is:
Uncaught Error: [$injector:unpr] Unknown provider: $$asyncCallbackProvider <- $$asyncCallback <- $animate <- $compile This is in angular.js:68 (the last return statement).
Unsure if I've done something a little whack, or if perhaps with a fresh node/ruby/bower install there's been some changes in the dependencies.