-
Notifications
You must be signed in to change notification settings - Fork 143
[worklets] import() method conflicts with new JavaScript feature #373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The import on the worklet allows the main thread to import scripts into other threads? So yes? It's analogous to workers. e.g. new Worker('foo.js');
CSS.paintWorklet.import('foo.js'); Inside the WorkletGlobalScope you'd use the dynamic import() function or just the regular import statement. |
There was debate a while ago if |
Okay, I got confused about the setup. Having some inline examples would help. And yeah, maybe a more specific term would be good. Something like "distributeScript"? To make it more clear it ends up running multiple times against several globals. |
Filed #374 and added an example section for what import actually does. |
Do we still need https://drafts.css-houdini.org/worklets/#dom-worklet-import with https://github.com/tc39/proposal-dynamic-import?
cc @domenic
The text was updated successfully, but these errors were encountered: