We are happy to announce the release of the new angular 1.2.0 package, which takes advantage of the new build process introduced in Meteor 1.2 to make Angular developers feel even more comfortable and productive.
The main difference between older versions is that now, we use Angular to process regular HTML and JS files instead of .ng.html and .ng.js.
We worked hard to make migrating an existing Angular app to Meteor easier. You can migrate by simply moving your entire existing project into Meteor, or also by using your own tools and connecting to a Meteor server, like we demonstrated with Ionic.
For existing users, as the HTML parsing is now happening by the angular package, we should rename all .ng.html files to .html and remove the blaze-html-templates package to reduce load time on the client.
Also, the new angular package processes JS files with Babel for Ecmascript 2015 support and ng-annotate out of the box.
It also adds the decorators syntax from Babel so it will be easier to use the pbastowski:angular2-now package. This lets you write Angular 2.0 syntax in your Angular 1.x application, which we recommend as a best practice.
That means we should rename all .ng.js files to .js and remove the default ecmascript Meteor core package from our projects.
The new package also uses the Meteor 1.2 caching compilers to make the build process faster.
If you still want to continue using the old build process and combine Blaze and Angular templates, you can use the angular-with-blaze package instead of the `angular` package and keep using the same ng.html and ng.js file extensions and the urigo:angular-blaze-template package to include Blaze templates inside your Angular templates.
Going forward to version 1.3, we will start changing our API to be directed into the best practices we’ve recommended:
Making the data API as similar as possible to the current and the future native Meteor API
Removing the autobind feature to get better performance out of the box
To get ready, you can start using your $meteorservices without autobind (sending false to that parameter).
Thanks for all the help we got from the community on this release!
We are happy to announce the release of the new angular 1.2.0 package, which takes advantage of the new build process introduced in Meteor 1.2 to make Angular developers feel even more comfortable and productive.
The main difference between older versions is that now, we use Angular to process regular
HTMLandJSfiles instead of.ng.htmland.ng.js.We worked hard to make migrating an existing Angular app to Meteor easier. You can migrate by simply moving your entire existing project into Meteor, or also by using your own tools and connecting to a Meteor server, like we demonstrated with Ionic.
For existing users, as the
HTMLparsing is now happening by theangularpackage, we should rename all.ng.htmlfiles to.htmland remove theblaze-html-templatespackage to reduce load time on the client.Also, the new
angularpackage processesJSfiles with Babel forEcmascript 2015support andng-annotateout of the box.It also adds the
decoratorssyntax from Babel so it will be easier to use thepbastowski:angular2-nowpackage. This lets you write Angular 2.0 syntax in your Angular 1.x application, which we recommend as a best practice.That means we should rename all
.ng.jsfiles to.jsand remove the defaultecmascriptMeteor core package from our projects.The new package also uses the Meteor 1.2 caching compilers to make the build process faster.
If you are using the
accounts-uipackage, we now havedotansimha:accounts-ui-angularpackage instead.If you still want to continue using the old build process and combine Blaze and Angular templates, you can use the
angular-with-blazepackage instead of the `angular` package and keep using the sameng.htmlandng.jsfile extensions and theurigo:angular-blaze-templatepackage to include Blaze templates inside your Angular templates.Going forward to version 1.3, we will start changing our API to be directed into the best practices we’ve recommended:
autobindfeature to get better performance out of the boxTo get ready, you can start using your
$meteorservices withoutautobind(sendingfalseto that parameter).Thanks for all the help we got from the community on this release!
Idan Wender, Chris Antoine, Eytan Manor, Caleb Cox, barbatus, Uri Goldshtein, Joseph Kimberger, Birk Skyum, Tally Barak, Dotan Simha, Netanel Gilad, dinesh36, DumpOfTheVar, Karim Abuzaid, marvinmarnold, David Carter, Eyal Ronel, MarkPhillips7, Nick Benes, Shawn Mckay, Erdou, Sompop Suksawat, Miloš Stanić, BEAUDRU Manuel, BrainCrumbz, David Yahalomi
Please let me know what you think in the comments below.