Support for AMD / CommonJS?

[balderdashy]

Support for AMD / CommonJS?

[robwormald]

I hadn't planned on it. Given Angular's module loader (which I realize is different than script loading) and a decent grunt build process, I've never felt the need for AMD/CommonJS, etc. Ditto for browserify - I tend to build my Angular apps as a separate entity to my Sails backend, and prefer to keep things segregated that way. Angular's Dependency Injection (DI) solves a lot of these issues as-is.

That said, I have no particular objection, so feel free to add it and submit a PR. Assuming it doesn't break default behaviors, I'm sure plenty of people would find it useful.

I'd be interested to hear more on this - pros and cons and whatnot.

[thebigredgeek]

We might be able to tool a separate build for each, drawing from the same codebase and pushing out to multiple artifact repos post-build. That being said, I think bower is enough when using AngularJS. AMD is a bit overkill, and actually makes the app more sluggish on mobile especially. Again, I would recommend doing this during build, and not shimming it to respond to various environments.

[CWyrtzen]

Greetings - can we closet this up or is there more discussion to be had?

Contribution Guide | Stackoverflow | Google Group | Trello | IRC | Build Status

[chiefy]

I agree with @robwormald and @thebigredgeek that AMD is probably overkill for Angular, so I'll close this. Thanks.

[CWyrtzen]

Thanks all!