Is your feature request related to a problem? Please describe.
I need to route different requests to different instances of the same WASM based on the URL. This is almost achievable with this package, except for the use of the JavaScript variable wasmhttp. Multiple WASMs fight the use of this
Describe the solution you'd like
The serve command needs to register itself against a manager that can handle multiple WASMs.
Additional context
Open to other ideas on how to run multiple instances of the same WASM. This has to be in the same service worker.
Bonus points if users of the library within the service worker can designate the IDs for the different WASM instances, and the library auto spawns a new instance of the WASM when there's no matching WASM with that ID
Is your feature request related to a problem? Please describe.
I need to route different requests to different instances of the same WASM based on the URL. This is almost achievable with this package, except for the use of the JavaScript variable
wasmhttp. Multiple WASMs fight the use of thisDescribe the solution you'd like
The serve command needs to register itself against a manager that can handle multiple WASMs.
Additional context
Open to other ideas on how to run multiple instances of the same WASM. This has to be in the same service worker.
Bonus points if users of the library within the service worker can designate the IDs for the different WASM instances, and the library auto spawns a new instance of the WASM when there's no matching WASM with that ID