Custom module loaders and script tags

Guy Bedford guybedford at googlemail.com
Sat Jun 8 12:56:28 PDT 2013


Would it be better simply to override the default system loader, or would
this be discouraged?

I notice Yehuda's examples are based on overloading of the System loader,
so perhaps this will be the standard method.

On 8 June 2013 06:47, Sam Tobin-Hochstadt <samth at ccs.neu.edu> wrote:

> On Fri, Jun 7, 2013 at 11:29 PM, Guy Bedford <guybedford at googlemail.com>
> wrote:
> > I'm trying to work out how custom module loaders can be used with
> standard
> > script tags.
> >
> > For example, say I create a RequireJS-style loader (with an identical
> > configuration API including map config etc), and want to use this within
> a
> > script file loaded via a script tag:
> >
> > <script>
> >   var RequireJSStyleLoader = new Loader({
> >     // ... etc ...
> >   });
> > </script>
> > <script src="some/module/file.js"></script>
> >
> > How do I configure the loader to know that "some/module/file.js" should
> have
> > its imports and module declarations applied with my custom loader
> > (RequireJSStyleLoader) and not the system loader?
> >
> > Or is it only possible to set a custom loader for imports executed with
> > RequireJSStyleLoader.load(...)?
>
> Currently, that's all that's possible. Dave and I plan to talk to
> people on the HTML side to enable this as well, but that has not yet
> begun.
>
> Sam
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20130608/94e097f7/attachment.html>


More information about the es-discuss mailing list