> I thought [modules] inclusion [in ES6] wasn't set in stone yet.... [And regarding lazy-loading], there will be some form of it for sure, I guess the question is at what granularity.
I'm pretty sure modules are in. Whether or when Node.js supports them will be an open question for a while, I guess. Lazy-loading details still seem to be a gray area in browsers, though. I am under the impression that for Angular 2.0 lazy loading isn't set in stone, yet. Last I read, Miško Hevery has an idea that they're toying with. > we're to using typescript at work now, it does (or at least you can get it to) generate AMD module definitions Is it possible that you didn't find the ability to use aliases and relative paths due to less than full support for AMD in typescript's generation? I don't actually know anything about it, just wondering. > Regarding browserify: if you're using node front to back I'd expect less pain with code reuse, nice win, I've researched but not spike it yet. I use browserify to get external Node libraries into a browser. For modules that I'm writing for both Node and the browser, where the browser app is a RequireJS-based, I use RequireJS/AMD syntax and amdefine ( https://github.com/jrburke/amdefine ). > Interesting no one mentioned google closure I love Closure Compiler/Closure Library modules for efficiency and type-checking and all of that good stuff. In some circumstances the efficiency gains are very valuable (e.g. gmail!). It doesn't on its own support lazy-loading, though, and in a big app I really want lazy loading. I have actually combined RequireJS lazy loading with Closure Compiler in an Angular app. It was a delicate combination, but it is possible. The issue for me with Closure Compiler is that it's tough to convince anyone to contribute to an open-source project that uses it (correctly) because it's got a pretty steep learning curve. > I'm still not convened that requirejs offers a maintainable approach to module separation on a massive code base If I were you, I'd go for RequireJS for the lazy loading, so I'm wondering -- do you mind sharing your concerns? I haven't picked up on your reasoning. You mention your gut, and of course one should consult the gut.... but is there anything specific you can point to? -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
