Support for Angular.js

[KyleMit]

angular-meteor requires that angular templates be placed in a file with extension *.ng.html in order to be parsed by the angular package and not be parsed by spacebars

Big request, but is there a way to allow users to add arbitrary folder/file names? This would also grant access to utilizing special directories like lib.

[sean-stanley]

Actually theoretically now with angular package version 1.2, you don't need to user .ng.html any more. You need to remove blaze and ecmascript and angular will take over rendering the .html templates.

Not sure this is possible with meteor pad either though as version 1.2 of meteor no longer requires the meteor-platform package but has instead broken this down into smaller packages allowing for better project customization. Unfortunately though I can't seem to load meteor-base instead of meteor-platform

+1 for angular js support though. I am having trouble with some tricky bugs that don't show up in codepen only in the angular environment.

[KyleMit]

@sean-stanley, it does seem like we're closer without the requirement that *.ng.html be used.

I've noticed that you can remove meteor-platform and add meteor-base and angular
^{*(after some additional loading and scrolling)}

Sample MeteorPad: http://meteorpad.com/pad/3Zs3psWjq6LbwW7Rk/

However, the project still won't work as nothing from the body gets delivered to the client. The problem seems to be related to the code in 1.2.0.1 vs 1.2.1.0

You can reproduced locally by running the following commands:

meteor create angular-todos --release 1.2.0.1
meteor remove blaze-html-templates ecmascript
meteor add angular
meteor list

However, building a 1.2.1.0 version will work locally (as well as on MeteorPad I suspect).

So the real request at this point is to add v1.2.1 - #40