-
Notifications
You must be signed in to change notification settings - Fork 19
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
WARNING: Tried to load angular more than once #3
Comments
Cheers Ahmad, I'll look into that this evening |
Thank you very much |
I've implemented a fix in v0.10.0 based on @renato's solution in angular-meteor issue #205. It seems to work a treat. |
Good job I will try it out |
Works fine thank you. |
Hi there, I'm still having this issue, I created a brand new project, then proceed on creating a route, it worked fine, but after I created a second route I get the error:
I have the
but still no fix to the issue. |
I can confirm this bug too, once I created the meteor-angular app with bower install options 'Yes'. Creating two consecutive routes with angular-meteor:route 'testroute2'; the first one loads well, where the second one comes up with: Tried to load angular twice error. |
I'll look into it |
hey guys, |
I was able to fix it by just making "bower": false in .yo-rc.json file {
"generator-angular-meteor": {
"filters": {
"js": true,
"html": true,
"css": true,
"pagination": true,
"framework": "bootstrap",
"bower": false,
"auth": true
},
"appname": "myApp"
}
} How do I verify my current generator version? |
that's very interesting.
|
can you give the latest version (0.20.3) a try? |
This happens when choose bower support and add package that depends on angular it self
this is related to issue #223 on angular-meteor repo
Suggested fix:
I think it would be perfect if the generator remove the dependency on mquandalle:bower and generate an independent package with mquandalle:bower in case of the user choose to add bower support,
and also add main files of bower to the cleint in package.js
The text was updated successfully, but these errors were encountered: