Alternative for polyfills: A loader that maps module names to alternate implementations. This reminds me of dependency injection.
Potential problem: The path of a (non-built-in) library might not always be a good ID (one module loads a minified version, another doesn’t). Maybe we need some kind of optional separate module ID. On Nov 3, 2011, at 20:17 , David Herman wrote: > Possibly, although it could be tough; I'll keep this in mind as we nail down > the API details. > > Dave > > On Nov 3, 2011, at 11:18 AM, Axel Rauschmayer wrote: > >> Can loaders be composed (e.g. to use several polyfills at the same time)? >> One might be able to chain them in some fashion. >> >>> Yes, good point about loaders. I would like a standard HTML way of >>> specifying a loader to use, so you could simply say: >>> >>> <meta loader="polyfill.js"/> >>> >>> and from then on your clients don't have to change a thing. >> >> -- >> Dr. Axel Rauschmayer >> [email protected] >> >> home: rauschma.de >> twitter: twitter.com/rauschma >> blog: 2ality.com >> >> >> > -- Dr. Axel Rauschmayer [email protected] home: rauschma.de twitter: twitter.com/rauschma blog: 2ality.com
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
