Re:Microsoft Edge supports ES6 modules
by eknkc on Tuesday May 17, 2016 @02:47PM
(#11716217)
I guess service workers might solve a lot of issues here. You could do weird stuff like basically serving a tar file for all assets and use a service worker to handle individual requests.
[ Parent
| on HN ]
Re:Microsoft Edge supports ES6 modules
by MatthewPhillips on Tuesday May 17, 2016 @02:52PM
(#11716255)
That's a really smart idea, I hadn't considered that. Once you add in caching you might get pretty reasonable performance.
Re:Microsoft Edge supports ES6 modules
by WorldMaker on Tuesday May 17, 2016 @03:54PM
(#11716812)
Also, the not yet implemented module loader spec would include a format similar to the AMD bundle format where modules are wrapped in calls to `System.register`.
Re:Microsoft Edge supports ES6 modules
by MatthewPhillips on Tuesday May 17, 2016 @04:13PM
(#11716997)
There's no such bundling format under consideration, as far as I'm aware. System.register is a SystemJS API, not a spec one.
Re:Microsoft Edge supports ES6 modules
by WorldMaker on Wednesday May 18, 2016 @09:45AM
(#11721848)
The Loader spec does include the concepts of a module registry and a low level API for them. From what I can tell skimming the specs, the high level construct of System.register has been in and out of the spec. Also from what I can tell, System.register may be possible to be implemented on top of the low level API regardless of whether it makes it into the final spec or not.
This is an interesting idea. On the other hand, I think if you started packing everything into a tar file, that could as well be a js file.
> On the other hand, I think if you started packing everything into a tar file, that could as well be a js file.
Modules give you a certain degree of namespacing, which is nice. Compiling down to a tar to be served to a Service Worker is undoubtedly easier than the mangling needed to remove the modules.