You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if there's any way to use this package without needing to assign our worker file to a <div /> to be "upgraded."
The problem is that our worker thread is being bundled via Webpack at the same time as the rest of our application and the output page is created using an HTML template. I'm not sure how it would be possible to assign the worker scripts to a div in this setup. Is there any way we can use the library in conjunction with the way Webpack bundles workers?
For reference, our code for creating our worker threads right now looks like this:
and then Webpack is automatically bundling the worker chunk and injecting it into the page without any input from us. Is there any way to leverage Worker-DOM together with the built-in Webpack worker loading functionality?
The text was updated successfully, but these errors were encountered:
It doesn't need to be a div specifically, but in order to use this package you need to assign a worker to a specific DOM node. In your template you'd need to specify the filepath of the generated worker bundle.
I'm wondering if there's any way to use this package without needing to assign our worker file to a
<div />
to be "upgraded."The problem is that our worker thread is being bundled via Webpack at the same time as the rest of our application and the output page is created using an HTML template. I'm not sure how it would be possible to assign the worker scripts to a div in this setup. Is there any way we can use the library in conjunction with the way Webpack bundles workers?
For reference, our code for creating our worker threads right now looks like this:
and then Webpack is automatically bundling the worker chunk and injecting it into the page without any input from us. Is there any way to leverage Worker-DOM together with the built-in Webpack worker loading functionality?
The text was updated successfully, but these errors were encountered: