[jsc-dev] ANN: ES6 Modules are enabled by default

[Yusuke SUZUKI]

As of r210016[1], we enabled ES6 modules by default.
We exposed it behind the runtime flag 5 weeks ago and it was shipped in
STP19.
After that, we fixed several minor issues. Now our implementaion passes
all the module related tests in Test262. And the major issues are fixed.

I hope it would become good infrastructure for the other features like HTML
imports. And it would be super nice if we can have great debugging features
for the modules in the inspector.

The next steps are the following,

1. TC39 is working on standardizing dynamic-imports. It gets much attension
and quickly becomes the stage 3 since it is a way to load ES6 modules
on-demand
and this is needed for a long time[2]. It would be good to prototype it on
the top
of our module implementaiton and give feedbacks to the proposal before the
proposal is introduced into the spec.

2. whatwg HTML is also standardizing ES6 modules for the Web Workers. It is
like,
`new Worker("..../.js", { type: "module" })`[3]. Worker refactoring done in
[4] will
pave the way for bringing our module loaders into the Web Workers.

3. WebAssembly modules (instance) can be integrated into the module pipeline
once the proposed design is stabilized[5].

If you find any bugs, please file it in bugs.webkit.org and ping me.
And thank you for your support!

[1]: https://trac.webkit.org/changeset/210016
[2]: https://github.com/tc39/proposal-dynamic-import
[3]:
https://html.spec.whatwg.org/multipage/workers.html#module-worker-example
[4]: https://bugs.webkit.org/show_bug.cgi?id=164425
[5]: http://webassembly.org/docs/modules/#integration-with-es6-modules

Best regards,
Yusuke Suzuki
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/jsc-dev/attachments/20161220/b3c40e18/attachment.html>