Allow for dynamic webpack public paths

According to the webpack docs, you can configure a dynamic public path for output files (like the web worker file) at runtime by adding __webpack_public_path__ = myRuntimePublicPath; to the top of your entry. However, this plugin generates a one-line entry e.exports = __webpack_public_path__ + "rustworker.worker.js".

It would be great if there were some configuration option for this plugin to allow adding the runtime public path override line to the generated entry.

[skmvasu]

@developit I’m also facing a similar problem. I’m publishing a library which internally uses a Sharedworker. When bundling this, the sdk.js, and my worker.js are generated.

The problem is when the client imports sdk.js, it’s part of it’s vendor bundle. However worker file is not on the clients public path.

This is the code that gets generated by the plugin:

    './node_modules/worker-plugin-shared/dist/loader.js?{"name":"0"}!./src/sdk/socket/worker.ts': function(
      e,
      t,
      n,
    ) {
      e.exports = n.p + 'js/0.70afebd5.worker.js';
    },

The generated worker file is not available in the publicPath of the client. Not sure how this can be handled. @developit any thoughts on how to handle this?

[skmvasu]

Makes sense. Thanks for taking a look 😃

We’re exploring a few options. Will update if something works.