jdmitchell at gmail.com
Tue Oct 8 13:25:07 PDT 2013
We deal with both build time as well as runtime dependency & bundling. Fwiw, for this we're also using the grunt toolchain for builds, etc.
The main trick we're using is that each version of each file is uniquely identified with a content hash of the file. We then shove all of this stuff into our own origin servers as well as cdn's. Then our bundling uses the explicit name for all of these resources and only the high level end points are generic/unversioned.
On Oct 8, 2013, at 4:30 AM, Gregory Alan Bolcer <greg at bolcer.org> wrote:
> On 10/7/2013 11:12 PM, John Mitchell wrote:
>> On Oct 7, 2013, at 10:47 PM, Bill Humphries <whump at mac.com> wrote:
>>> On Oct 7, 2013, at 10:44 PM, John Mitchell <jdmitchell at gmail.com> wrote:
>>>> FWIW, I do agree that for most people Ember's approach to things like templating is more approachable. Angular takes a bit of work to internalize it's approach.
>>> How do you do dependency and module management with Angular?
>> Our case is a bit odd in that we're building our own "framework" on top of Angular for use by various internal and external teams so we're doing modularization, dependency management, and the whole bootstrapping thing ourselves. We have a server-side packager that works in conjunction with our own client-side bootstrapping "shell" in which the various modules are pulled down on-demand.
>> FoRK mailing list
> greg at bolcer.org, http://bolcer.org, c: +1.714.928.5476
> FoRK mailing list
More information about the FoRK