Since there is no intent-to-ship-modules thread in V8 (and since this intent brings module support into HTML as well as scripts and not just one or the other), I think the test262 question is very much appropriate in this thread (you may disagree, but I may, too ;)).
☆*PhistucK* On Wed, Jun 21, 2017 at 6:25 PM, Domenic Denicola <d...@domenic.me> wrote: > From: blink-...@chromium.org [mailto:blink-...@chromium.org] On Behalf Of > PhistucK > > > What about test-262 (web-platform-tests are not supposed to test > ECMAScript features) for modules? > > This is not an ECMAScript feature; this is an intent-to-ship specifically > for <script type=module>, and HTML feature. As such test262 tests are out > of scope. > > There are some test262 tests for modules, but those are related to > foundational work done by the V8 team earlier in the process, and not > related to the work being done in this intent to ship. > > > Also, how does this integrate with service workers? Is there a type or > something that signals that the fetch event is for a module fetch? > > <script type=module> is just another script. There is no special treatment > for them in service workers or at the network layer. > > (If you have further questions of this sort, perhaps ask them on the > specification repo or StackOverflow; we should probably not get into a > tutorial on the modules spec here.) > > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
