Skip to content
This repository was archived by the owner on Sep 9, 2021. It is now read-only.

[Feature] support ModuleWorkers #67

Closed
TrySound opened this issue May 3, 2017 · 4 comments
Closed

[Feature] support ModuleWorkers #67

TrySound opened this issue May 3, 2017 · 4 comments

Comments

@TrySound
Copy link
Contributor

TrySound commented May 3, 2017

https://html.spec.whatwg.org/multipage/workers.html#module-worker-example

@michael-ciniawsky michael-ciniawsky changed the title Consider using spec compatible modules [Feature] support ModuleWorkers Oct 12, 2017
@michael-ciniawsky michael-ciniawsky added this to the 2.0.0 milestone Oct 12, 2017
@Narvey
Copy link

Narvey commented Apr 24, 2018

Yuck, so the readme says to do import Worker from './file.worker.js';, but you actually can't yet?

@michael8090
Copy link

michael8090 commented Feb 1, 2019

For now worker-loader doesn't support cross origin files, maybe we can support it by:

  1. using new Worker('https://some.other.origin/my-worker-script.js', {type: 'module'}), or
  2. using JSONP

What do you guys think?

@raphaelbs
Copy link

Chrome 80 shipped with support for this: https://www.chromestatus.com/feature/5761300827209728

How about adding an option to enable it? Jason Miller made this gist to check support for module workers.

@alexander-akait
Copy link
Member

Done #255, you can set worker options, docs will be updated in the near future

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants