Skip to content

angular-loading-bar not working with generator-angular-fullstack #349

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sethlesky opened this issue Jul 14, 2014 · 4 comments
Closed

angular-loading-bar not working with generator-angular-fullstack #349

sethlesky opened this issue Jul 14, 2014 · 4 comments
Labels

Comments

@sethlesky
Copy link

Following the install instructions (https://github.com/chieffancypants/angular-loading-bar) on a fresh install of angular fullstack and I get the follow unhelpful error in the browser.

I've also opened an issue on angular-loading-bar, as I'm unsure of the cause.

Uncaught object angular.js:78
(anonymous function) angular.js:78
(anonymous function) angular.js:3857
forEach angular.js:325
loadModules angular.js:3823
createInjector angular.js:3763
doBootstrap angular.js:1415
bootstrap angular.js:1430
angularInit angular.js:1343
(anonymous function) angular.js:21773
fire jquery.js:3119
self.fireWith jquery.js:3231
jQuery.extend.ready jquery.js:3443
completed
@kingcody
Copy link
Member

@sethlesky, I just generated a project answering yes to all questions (jade, less). Then I ran bower install --save angular-animate angular-loading-bar. I then added:

'ngAnimate',
'angular-loading-bar'

to my main module dependencies in client/app/app.js

I ran grunt serve and I was pleasantly greeted by an angular-loading-bar. Does this procedure mirror yours? Also, I received no error in my browser console.

@DaftMonk
Copy link
Member

@sethlesky DI errors for some reason only fire a very non specific 'Uncaught object angular.js' error in chrome. If you open the page in firefox you should see a more detailed stack trace.

That said, it sounds like you may have forgotten to include the module as a dependency in your app.js

@sethlesky
Copy link
Author

@DaftMonk @kingcody Seeing the full error in Firefox was helpful. The issue was not having correctly added ngAnimate to bower.json. Thanks a ton.

@kingcody
Copy link
Member

Thank you @sethlesky, shedding light on the angular-loading-bar. I really like nProgress and when using angular, that module couldn't be easier to get going. I'll most like likely be using it in my own fullstack projects :)

If this solves your issue, would you mind closing it? Thanks again and best of luck!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants