-
Notifications
You must be signed in to change notification settings - Fork 390
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
Feature Request: Expose endpoint #405
Comments
That should definitely be easy. I am now wondering if I should remove Lemme think about this for a bit. |
Any updates on this? |
Check the pull request I just submitted #487 it'll allow to simply do : myProxy.terminate(); |
After @surma 's review of my first attempt, I've built this one on comlink-loader GoogleChromeLabs/comlink-loader#27. Still waiting for it to be approved or rejected though |
Related to #372
Although there are ways of getting around this, it would make things much more convenient to expose the endpoint on a proxy property. I'm using comlink-loader, which makes it impossible to access the original WebWorker instance.
What I'd love is something like:
I imagine this would be easy enough to implement. Hoping you think so too! :)
The text was updated successfully, but these errors were encountered: