1247687 - Implement worker modules

Status: NEW

(Core :: DOM: Workers, task)

Description

[Jon Coppeard (:jonco)]

Allow workers to execute module scripts too.

Proposed spec: https://github.com/whatwg/html/pull/608

Comment 1

[tobias.buschor]

That would be really useful

Comment 2

[709922234]

chrome bug: https://bugs.chromium.org/p/chromium/issues/detail?id=680046

>> Spec of Dedicated/SharedWorkers:
>> https://html.spec.whatwg.org/multipage/workers.html#module-worker-example

>> Spec of ServiceWorkers (see "type" in the section):
>> https://w3c.github.io/ServiceWorker/#service-worker-concept

Comment 5

[:Ms2ger (he/him; ⌚ UTC+1/+2)]

Does this actually need JS engine changes?

Comment 6

[Jon Coppeard (:jonco)]

No, all the work is in the embedding.

Comment 7

[tobiasuhlig78]

Any updates on this one?

The Chromium team already flagged the ticket for version 80.

Definitely a +100 for the priority of this ticket on my end (creating a web workers driven es8 framework).
In FF, the only chance to get it running is Webpack.

Comment 8

[tobiasuhlig78]

A quick update on the current status would be appreciated.

The new framework is online now and alreadyat 227 github stars (December 20) :
https://github.com/neomjs/neo

Here are the online examples, which according to the specs should work in every modern browser:
https://neomjs.github.io/pages/

It makes me a bit sad to see FF falling behind on an such important topic.

Hoping you will catch up!

Best regards
Tobias

Comment 9

[Eriko Kurimoto]

Chromium will send an intent to ship ES modules for Shared Workers.
(crbug: https://bugs.chromium.org/p/chromium/issues/detail?id=824646)

We are considering FireFox is positive for supporting this feature since the specification discussion (https://github.com/whatwg/html/pull/608#issuecomment-183003447).
If there is misunderstanding or any updates, please let us know.

Comment 10

[Andrew Sutherland [:asuth] (he/him)]

As part of overhauling the scriptloader to support modules we'd also like to try and reduce code duplication between the worker scriptloader and the main-thread window scriptloader. Much of the complexity in the worker scriptloader relates to 2 things:

1. Channels can't be opened on worker threads. Bug 1528285 will address this so we want to wait on that.
2. Loading ServiceWorker scripts from Cache API storage does not look like using a channel. For this, a tentative plan to investigate is to create a dedicated channel type for loading scripts from the Cache API. This could help normalize things from the script loader's perspective.
   • This may or may not also dovetail with the need for there to be a Worker equivalent to DocumentChannel for ServiceWorker and SharedWorker cases where we need to know the COEP header value before we select the process to spin up the worker.

Comment 11

[tobias.buschor]

Chromium Status: Fixed
https://bugs.chromium.org/p/chromium/issues/detail?id=824647

Webkit Status: Fixed
https://bugs.webkit.org/show_bug.cgi?id=164860

Both will ship soon!

Comment 12

[tobiasuhlig78]

wrote a short blog post on this topic:
https://levelup.gitconnected.com/safari-webkit-about-to-release-support-for-js-modules-inside-the-worker-scope-9dd33fc20190?source=friends_link&sk=db61a01446ca5a51ee2f932aad9ca890

right now, the rendering performance of firefox worries me even more than the missing JS module support for workers.

best regards,
tobias