-
Notifications
You must be signed in to change notification settings - Fork 624
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
angular-meteor doesn't work with meteor 1.3 #1277
Comments
Yeah, this is a known error. Should be fixed soon. |
im totally stuck with my project now. Changes to your project's package version selections: autopublish removed from your project autopublish: removed dependency While selecting package versions:
` |
You can try to use angular from npm instead of atmosphere. By angular, I mean angular, not angular-meteor. It should fix the problem. |
How do you use angular from npm with Meteor 1.3. I installed angular from npm and attempt to import it (import angular from angular) and get this error in the console: |
@kamilkisiela i have same issue give me some guide how can i fix this using npm ? |
@JeremyBYU, @Furqankhanzada Here is what I have done to install angular-meteor and angular via npm.
|
@danimbrogno Keep in mind that since you use |
@ozsay good point! Do you know offhand what the impact would be if one were to use angular-babel instead of ecmascript? You would gain annotations, but would some other feature be lost? Is angular-babel compatible with 1.3? |
Thanks for your instruction @danimbrogno . I got it working but I had to also do the following.
One little thing I noticed is that I can see the browser transition from {{greeting}} to "Welcome". What I'm trying to say is that I can visually see angular compile the templates and such, lasts about 1/2 second. Is that normal? P.S I also switched out ecmascript pacakge like so
Now ng annotate works fine! |
Is issue with showing angular uncompiled tags while angular loads still case? |
+1 |
@JeremyBYU, I think this might help: |
@riongull Yep that seems like it should do the trick, thanks. |
I'm having issues with importing and the same warning.. WARNING: Tried to load angular more than once. I'm thinking that some of the packages (ie. angular-meteor-auth, angularui:angular-ui-router) means that angular is added as a dependency and appears in my versions file. Is there a way around this? |
@riongull Im afraid that ng-cloak does not help there - after updating to meteor 1.3 my applications render white with index.html navigation buttons visible and unstyled - every button is seen, even those hidden by angular for good second, before application initializes - adding or removing fast render makes no difference, there is ng-cloak in my navigation section - doesn't help |
Hi everyone. |
@Urigo Working perfectly for me from Atmosphere :) Just struggling to get my head around the whole npm thing! Is it best to stick with Atmosphere packages for the time being? |
@Urigo There should be invitation to my repository on Your emai. If You could check out why navigation is shown, before code is compiled. It didn't happened before upgrade to meteor 1.3 |
@TWKDreamState Feel free to use npm 👍 @jmwierzbicki Can you try with latest release which is |
still same case: this is my nav bar code:
list of packages:
as a reminder, this issue appeared whenever i upgraded to 1.3 , even since RC1, and disappeared when i downgraded meteor to 1.2 again. |
@jmwierzbicki Could you send me some repro of this? |
This may happen because Meteor 1.3 puts |
well, is it possible to alter this behavior? |
@jmwierzbicki You can use ngCloak. But I recommend you to create a main component, let's call it So if you have something like this: <body>
<div ng-controller="MainCtrl"> {{ hello }} </div>
</body> It will become: <body>
<app></app>
</body> Where a template of <div ng-controller="MainCtrl"> {{ hello }} </div> It's always nice to use function onReady() {
angular.bootstrap(document, [
'your-app-name'
], {
strictDi: true
});
}
angular.element(document).ready(onReady); This way your whole application won't be showed up until document is fully ready. |
About changing this behaviour. Hmm you can check that PR |
not sure why, but im getting angular.module(...).component is not a function |
|
Thanks, its all working now! |
I spent few hours digging up through packages, and there is what i found:
Im creating tutorial step 3 app for testing purposes:
unpacking zip
after that im upgrading meteor and downloading packages:
meteor update --release METEOR@1.3-rc.2
strangely it downloaded angular-meteor 1.3.1 :
root@debian:/opt/testapp2# meteor list
angular 1.3.1* Everything you need to use AngularJS in your Me...
autopublish 1.0.5-rc.2 (For prototyping only) Publish the entire ...
es5-shim 4.5.8-rc.2 Shims and polyfills to improve ECMAScript ...
insecure 1.0.5-rc.2 (For prototyping only) Allow all database ...
jquery 1.11.6-rc.2 Manipulate the DOM using CSS selectors
meteor-base 1.0.2-rc.2 Packages that every Meteor app needs
mobile-experience 1.0.2-rc.2 Packages for a great mobile user experience
mongo 1.1.5-rc.2 Adaptor for using MongoDB and Minimongo ov...
session 1.1.3-rc.2 Session variable
standard-minifier-css 1.0.4-rc.2 Standard css minifier used with Meteor app...
standard-minifier-js 1.0.4-rc.2 Standard javascript minifiers used with Me...
tracker 1.0.11-rc.2 Dependency tracker to allow reactive call...
after that i manually updated angular:
meteor add angular@=1.3.7
Changes to your project's package version selections:
angular upgraded from 1.3.1 to 1.3.7
angular-meteor-data upgraded from 0.0.8 to 0.3.0
angular-templates* upgraded from 0.0.3 to 1.0.0
pbastowski:angular-babel upgraded from 1.0.7 to 1.0.9
from now on, browser throw "angular module not found" basically wall of error: http://pastebin.com/Bk3STyTQ
when downgrading angular to 1.3.1 i got
Changes to your project's package version selections:
angular downgraded from 1.3.7 to 1.3.1
angular-templates* downgraded from 1.0.0 to 0.0.3
and browser error was exactly same as on 1.3.7
So i manually downgraded angular-meteor-data down to 0.0.8 and this made it working once again.
The text was updated successfully, but these errors were encountered: